On 7/27/05, Larry Ewing <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-07-27 at 07:39 -0400, Bryan Mayland wrote:
> > Larry Ewing wrote:
> >
> > >Sigh, after all these years you'd think I could get a diff right,
> > >clearly the patch I sent before was reversed, here is the correct patch.
> > >
> > >
> >     hehe yeah I noticed that.  The code isn't right though, but I didn't
> > realize what it was trying to do either the first time I saw it.  What
> > we're looking for there is the host bus the card is on, not the card
> > itself.  The idea is to determine of the PCI bus itself is considered
> > buggy and adjust parameters on it accordingly.  Do you not have a
> > 0:00:00.0 device in your lspci?
> >
> 
> I don't appear to.  I've attached the lspci output from that machine.
> 
> >     You're right, the code that is there is wrong though.
> >
> 
> --Larry

"Shades of PCI Bridge troubles Batman, it looks like the Riddles has returned!"

Strange listing:

a) PCI Bus #1 is missing.
b) Bus 0 - devices 0-5 are missing

It might be good to post back the output of pci -vv but trim it to
show on'y the PCI-PCI bridges. For instance here's one bridge in my
problematic machine:

0000:00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
(prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
        I/O behind bridge: 00009000-00009fff
        Memory behind bridge: f8000000-f9ffffff
        Prefetchable memory behind bridge: f0000000-f7ffffff
        BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-

The 'Bus:' section let's us see which bridges are creating the network
on the way to the video device.

- Mark


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to