Davide Libenzi wrote:
> It does not look right to me either to poke the IDE controller. Another
> solution might be to parse the routing table and gather informations from
> there. Example, the findings of 0x61,...,0x63 will tell us that we're
> dealing with newer chipsets that uses those for values for the 3 OHCI and
> the EHCI.
(The "plain" 650 [with 961] has no EHCI; this was introduced with the 962)
> The revision ID trick seems not effective, at least looking at
> your machine with rev-id 0 that has 0x61..63. Martin, was the revision id
> 0, that you suggested to be handled with the old router, minded ?
What about gathering all that info from the routing table? Please excuse
this perhaps naive assumption, but isn't that what's it's good for?
Thomas
--
Thomas Winischhofer
Vienna/Austria
mailto:[email protected] *** http://www.winischhofer.net
mailto:[email protected]
On Wed, 28 May 2003, Thomas Winischhofer wrote:
> Davide Libenzi wrote:
> > It does not look right to me either to poke the IDE controller. Another
> > solution might be to parse the routing table and gather informations from
> > there. Example, the findings of 0x61,...,0x63 will tell us that we're
> > dealing with newer chipsets that uses those for values for the 3 OHCI and
> > the EHCI.
>
> (The "plain" 650 [with 961] has no EHCI; this was introduced with the 962)
It still has 0x60...0x63 values in the routing table (looking at your
files).
> > The revision ID trick seems not effective, at least looking at
> > your machine with rev-id 0 that has 0x61..63. Martin, was the revision id
> > 0, that you suggested to be handled with the old router, minded ?
>
> What about gathering all that info from the routing table? Please excuse
> this perhaps naive assumption, but isn't that what's it's good for?
That's what's I'm telling ;) Now (in my office) I do not have the machine
to play with (personal laptop) but tonight I'll make a patch that will use
the routing table info to discover the appropriate router selection.
- Davide