lkml.org 
[lkml]   [2002]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] 2.5.17 /dev/port
Date
From
> On non-Intel platforms, with no dedicated IOIO opcodes, IOIO is
> usually implemented as a specific memory range. In that case, the
> only way to allow user-space access to it would be to mmap() that
> range... which means iopl() inb() and outb() on those platforms might
> be implemented either as open, readp and writep, respectively, or by
> iopl() being open() followed by mmap().

mmap and some other logic in certain cases. An outb stalls until the I/O
hits the device even on PCI. Either way thats really about what you
put into /dev/port (either the i/o logic or a map of /dev/mem with slightly
tweaked args)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

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