Messages in this thread | | | Subject | Re: [PATCH] 2.5.17 /dev/ports | Date | Wed, 22 May 2002 18:46:59 +0100 (BST) | From | Alan Cox <> |
| |
> BTW> Under java it's rather hard to get around > CAP_RAWIO if you ask me without going down to JNI.
People run them as root. Thats not rocket science
> > I've seen it used in tools written in java, python, perl, even tcl > > > > Other examples include libieee1284, the pic 16x84 programmer, hwclock, > > older kbdrate, /sbin/clock on machines that don't have /dev/rtc. > > All the examples above are samples of bad coding practice - I have > uncovered already here in C what can be expected inside there!
Portable code is good practice.
> > Not everything in the world is an x86, and not every app wants to be Linux/x86 > > specific or use weird syscalls > > Yes and in esp. everything in the world is a __m68000__!
When you look at the kernel codebase its abundantly obvious that its much more "if its not 32bit with hardware managed caches, little endian, with no more than one root pci bridge, has a 32/64bit machine word, is byte addressed, has sane store ordering rules, conventional not reverse mapped mmu, machine word sized cache coherency, and no more than 3 level page tables" and so forth its going to be hard to get it to work well.
A lot of that /dev/port using code is portable to everything from Minix through most BSD's. It works on pretty much anything with PC style devices.
Alan - 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/
| |