LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 10-07-2012, 10:52 AM   #1
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,508

Rep: Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571
What is AMD device 1002:7914


It's all in the subject. It's part of an RS690 Northbridge, about which I know squat
Quote:
00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (Internal gfx)
00:04.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI Device 7914
00:05.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (PCI Express Port 1)
00:06.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (PCI Express Port 2)
 
Old 10-07-2012, 12:22 PM   #2
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,597
Blog Entries: 2

Rep: Reputation: 4058Reputation: 4058Reputation: 4058Reputation: 4058Reputation: 4058Reputation: 4058Reputation: 4058Reputation: 4058Reputation: 4058Reputation: 4058Reputation: 4058
The PCI ID database sadly has no entry for that device, but since all devices in the range from 7912-7919 are listed as PCI to PCI bridges it is save to assume that your device also is one.
 
1 members found this post helpful.
Old 10-07-2012, 09:21 PM   #3
replica9000
Member
 
Registered: Jul 2006
Location: Quahog, Rhode Island
Distribution: Debian 'Sid', FreeBSD, Android
Posts: 664
Blog Entries: 2

Rep: Reputation: 115Reputation: 115
I think it's a Standard Hot Plug PCI Controller
 
Old 10-08-2012, 02:57 AM   #4
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,508

Original Poster
Rep: Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571
Thanks - I'll go for the pci-pci bridge as a most likely option.

I don't think it's a Hotplug controller, because this is a Northbridge thing, and everything pci is on the Southbridge. On the Northbridge I only have ram, & pcie video.
 
Old 10-08-2012, 12:49 PM   #5
replica9000
Member
 
Registered: Jul 2006
Location: Quahog, Rhode Island
Distribution: Debian 'Sid', FreeBSD, Android
Posts: 664
Blog Entries: 2

Rep: Reputation: 115Reputation: 115
I could be wrong, but I think it's a subsystem of the PCI-PCI bridge.

Code:
00:04.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:7914] (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=10, subordinate=10, sec-latency=0
	Memory behind bridge: d0000000-d00fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp
Code:
pcieport 0000:00:04.0: setting latency timer to 64
pcieport 0000:00:04.0: irq 40 for MSI/MSI-X
pcieport 0000:00:05.0: setting latency timer to 64
pcieport 0000:00:05.0: irq 41 for MSI/MSI-X
pcieport 0000:00:06.0: setting latency timer to 64
pcieport 0000:00:06.0: irq 42 for MSI/MSI-X
pcieport 0000:00:04.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:04.0: restoring config space at offset 0x8 (was 0x0, writing 0xd000d000)
pcieport 0000:00:04.0: restoring config space at offset 0x7 (was 0x101, writing 0x1f1)
pcieport 0000:00:04.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:04.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:05.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:05.0: restoring config space at offset 0x8 (was 0x0, writing 0xcff0cc00)
pcieport 0000:00:05.0: restoring config space at offset 0x7 (was 0x101, writing 0x3121)
pcieport 0000:00:05.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:05.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:06.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:06.0: restoring config space at offset 0x8 (was 0x0, writing 0xc800c800)
pcieport 0000:00:06.0: restoring config space at offset 0x7 (was 0x101, writing 0x1f1)
pcieport 0000:00:06.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:06.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:04.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:04.0: restoring config space at offset 0x8 (was 0x0, writing 0xd000d000)
pcieport 0000:00:04.0: restoring config space at offset 0x7 (was 0x101, writing 0x1f1)
pcieport 0000:00:04.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:04.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:05.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:05.0: restoring config space at offset 0x8 (was 0x0, writing 0xcff0cc00)
pcieport 0000:00:05.0: restoring config space at offset 0x7 (was 0x101, writing 0x3121)
pcieport 0000:00:05.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:05.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:06.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:06.0: restoring config space at offset 0x8 (was 0x0, writing 0xc800c800)
pcieport 0000:00:06.0: restoring config space at offset 0x7 (was 0x101, writing 0x1f1)
pcieport 0000:00:06.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:06.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:04.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:04.0: restoring config space at offset 0x8 (was 0x0, writing 0xd000d000)
pcieport 0000:00:04.0: restoring config space at offset 0x7 (was 0x101, writing 0x1f1)
pcieport 0000:00:04.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:04.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:05.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:05.0: restoring config space at offset 0x8 (was 0x0, writing 0xcff0cc00)
pcieport 0000:00:05.0: restoring config space at offset 0x7 (was 0x101, writing 0x3121)
pcieport 0000:00:05.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:05.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
pcieport 0000:00:06.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1)
pcieport 0000:00:06.0: restoring config space at offset 0x8 (was 0x0, writing 0xc800c800)
pcieport 0000:00:06.0: restoring config space at offset 0x7 (was 0x101, writing 0x1f1)
pcieport 0000:00:06.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10010)
pcieport 0000:00:06.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
 
Old 10-09-2012, 02:59 AM   #6
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,508

Original Poster
Rep: Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571
You have one too?

Going on recent kernel errors, it may just be an 'invisible pci bridge' that got a mention at some point. I have some of these (kernel errors) and they're intruiging.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Screen tearing on Ubuntu 12.04(32-bit) with AMD A4-3400 APU and AMD Radeon 6410D PhantomTurtle Linux - General 4 08-25-2012 08:09 PM
LXer: Build Sun xVM 3.4.2 from source on top OSOL 1002-128a LXer Syndicated Linux News 0 12-12-2009 01:01 AM
LXer: Setup OpenSolaris 1002-127 PV DomU at Xen 3.4.2 & Libvirt 0.7.1-15 (2.6.31.6 pv LXer Syndicated Linux News 0 12-02-2009 12:20 PM
LXer: Setup Fedora 12 RC3 PV DomU at xVM 3.3.2 Dom0 OpenSolalris 1002-126 LXer Syndicated Linux News 0 11-11-2009 07:40 PM
compile xmgrace on Fedora10 failed: Motif >= 1002 compatible API. centguy Linux - Software 9 08-22-2009 09:40 AM


All times are GMT -5. The time now is 09:47 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration