lkml.org 
[lkml]   [1999]   [Jan]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kmalloc
Hello Gerard,

> The address values provided in the pcidev structure qualified as 'suitable
> for ioremap()' looks rather a bad hack than a clean abstraction to me and
> it is not enough for all drivers to be portable. A driver needs some
> handle to access the device and, as I just wrote twice:), may also need
> the _actual_ configured PCI base addresses, but does not care of your
> obscure cookie that just make sense as input of some kernel routine.

These are not obscure cookies, but real physical addresses.

> All this stuff is to be redesigned for 2.3/4, in my opinion.

Sure. I was talking about this as a right solution for 2.2. In 2.3, we finally
need to make kernel understand there can be multiple buses, each of them using
either a different phys<->bus mapping or an IOMMU. I started working on a new
set of I/O functions, but for now I have to do some exams first.

Have a nice fortnight
--
Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
"Where the heck is the ANY key????"

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.104 / U:1.888 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site