Re: Prototype board patch for 2.0 kernel--needs to be updated for the 2.4..26 version

From: Gregg C Levine (drwho8_at_att.net)
Date: 05/23/04 

Date: Sun, 23 May 2004 14:56:00 GMT

Gregg C Levine
Thank you!!! I knew once I realized what you were getting at earlier, that we'd both
realize the obvious. And yes that author's patch was a mess. But was written a long
time ago, before the device drivers were reorganized.
Gregg C Levine drwho8 atsign att dot net

In article <2hbj11Fb29p9U1@uni-berlin.de>, Jens.Toerring@physik.fu-berlin.de
says...
>
>Gregg C Levine <drwho8@att.net> wrote:
>> A good point.... The site is
>> ftp://ftp.ibiblio.org/pub/linux/apps/circuits/!INDEX.html
>> You then need to look for Prototype-1.0.tar.gz. That contains examples, a
>> kernel patch to enable the 2.0 kernel to read the prototype board. The
>> author has abandoned it, he's not even listed in any of the currently
>> searchable directories. That's what I was writing about.
>
>Oiiii, that's horrible stuff. I don't mean that it's difficult to
>understand what happens there but there's a buffer overrun in the
>initialization routine, the initialization routine expects a long
>argument (but which is never used) and gets called with void...
>This kind of stuff definitely does not belong into the kernel via
>a patch. I guess the auther didn't realize that the stuff can be put
>into a module, but it's rather simple to convert it into one.
>You can download it from
>
>http://www.physik.fu-berlin.de/~toerring/IoPort.tar.gz
>
>In the Makefile you may have to change the settings for IOPORT_ADDRESS
>and IOPORT_MAJOR. If you need more instructions how to get it to run
>send me an email. And it's meant to work with 2.4 kernels and there
>are still quite a few things in there that I usually wouldn't do, e.g.
>access IO ports without checking that they aren't already in use by
>another modules etc. So better be careful, you can mess up a lot of
>things otherwise.
>
>But, basically, that module is superfluous, you can get the same
>effects from userland (at least if you have root privileges) when you
>use the functions iopl(2) to get access to the IO-ports and outb_p(2)
>and inb_p(2) to write to or read from the port.
>
> Regards, Jens
>--
> \ Jens Thoms Toerring ___ Jens.Toerring@physik.fu-berlin.de
> \__________________________ http://www.toerring.de

Relevant Pages

  • Re: RT patch acceptance
    ... judge the complexity of a design for that type of system. ... claim that you cannot judge the complexity of a kernel modification. ... Since the patch in question doesn't actually need that information to ... nanokernel's API up to date with additions to Linux's API that RT people ...
    (Linux-Kernel)
  • Re: inline asm semantics: output constraint width smaller than input
    ... Now in this case the patch you suggest might end up hurting the end result ... The below patch is to build the kernel for x86_64, ... # Device Drivers ... # PCI IDE chipsets support ...
    (Linux-Kernel)
  • [RFC] Making percpu module variables have their own memory.
    ... Someone using the -rt patch found that one of the tracing options caused ... 64K for every CPU to cover all the per_cpu variables used in the kernel ... static void wakeup_softirqd_prio ...
    (Linux-Kernel)
  • Re: This is [Re:] How to improve the quality of the kernel[?].
    ... The -mm kernel already implements what your proposed PTS would do. ... If patch have no TS ID, ... Thus i can apply for example lguest patches and implement and test new ... How many open source projects use Bugzilla and how many use the Debian BTS? ...
    (Linux-Kernel)
  • Re: Documentation - how to apply patches for various trees
    ... >> explanation of the various kernel trees and how to apply their patches. ... +a patch to the kernel or, more specifically, what base kernel a patch for ... +and what new version the patch will change the source tree into. ...
    (Linux-Kernel)