From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Corey Minyard <minyard@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] IPMI driver for Linux
Date: 21 Aug 2002 17:02:44 +0100 [thread overview]
Message-ID: <1029945764.26845.93.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3D63B612.8020706@acm.org>
On Wed, 2002-08-21 at 16:47, Corey Minyard wrote:
> I have been working on an IPMI driver for Linux for MontaVista, and I
> think it's ready to see the light of day :-). I would like to see this
> included in the mainstream kernel eventually. You can get it at
> http://home.attbi.com/~minyard. It should work on any kernel version,
> although you will have to fix up the Config.in and Makefile, and the
> Configure.help stuff may not work (it's currently in the 2.4 location).
>
> The web page has documentation on the driver, and documentation is
> included in the patch, too. This is a fairly full-featured driver with
> a watchdog, panic event generation, full kernel and userland access to
> the driver, multi-user/multi-interface support, and emulators for other
> IPMI device drivers.
Comments in general.
It touches user space with spinlocks held -> bad idea
It doesnt check copy_*_user returns instead commenting that some other
driver didnt so it wont - bad idea too
It seems to be allocating a major - can you have > 1 ipmi per host, can
it use misc devices, can it get one registered properly with lanana
Otherwise its way way way nicer than the hideous thing a certain chip
vendor sent me.
next prev parent reply other threads:[~2002-08-21 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 15:47 Corey Minyard
2002-08-21 16:02 ` Alan Cox [this message]
2002-08-21 16:52 ` Corey Minyard
2002-08-21 19:28 ` Preempt kernel patch for 2.4.19? Jurgen Kramer
2002-08-21 19:32 ` J Sloan
2002-08-21 20:41 ` J Sloan
2002-08-27 14:55 ` [patch] IPMI driver for Linux Pavel Machek
2002-08-27 22:14 ` Matthew Dharm
2002-08-28 2:01 ` Corey Minyard
2002-08-21 20:41 Larry Butler
2002-08-21 20:53 ` Corey Minyard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1029945764.26845.93.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®