Brad Parker wrote:
>
> Steve Longerbeam wrote:
> >
> >--------------3FD8AC989C7C80185F008685
> >Content-Type: text/plain; charset=us-ascii
> >Content-Transfer-Encoding: 7bit
> >
> >Alan Cox wrote:
> >
> >> > Drivers can keep track of this kind of information themselves,
> >> > and that is what I tell every driver author to do who complains
> >> > of a lack of a "bus_to_virt()" type thing, it's just lazy
> >> > programming.
> >>
> >> I'd agree. There are _good_ reasons for having reverse mappings especially o
> >n
> >> certain architectures, but thats for stuff like cache management. Its stuff
> >> the drivers have no business poking their noses directly into
> >>
> >
> >Which brings us back to the OHCI driver using a hash table to
> >store bus-to-virt entries? The *BSD driver does this.
>
> I think it makes more sense to rewite the OHCI driver to remember
> the mapping...
>
> I may just go off and do this.
>
Beside the problem with the done list, this should be easy.
The main reason why I have used the back mapping (bus_to_virt()) was
that the TDs and EDs are 8 words big now. When they remember the
mapping they need twice as much space (on 32 Bit machines).
But I think it might was the wrong design goal and 'simple/fast' is
a better goal here. Also because the number of TDs/EDs could be high in
theory
in praxis the quantity is not so large.
- Roman
> -brad
>
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
