From: Stephen Hemminger <shemminger@osdl.org>
To: joe briggs <jbriggs@briggsmedia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: binary kernel drivers re. hpt370 and redhat
Date: Wed, 27 Aug 2003 14:57:55 -0700 [thread overview]
Message-ID: <20030827145755.7e1ce956.shemminger@osdl.org> (raw)
In-Reply-To: <200308271840.30368.jbriggs@briggsmedia.com>
On Wed, 27 Aug 2003 18:40:30 -0400
joe briggs <jbriggs@briggsmedia.com> wrote:
> I have a client who has a raid controller currently supported under windows,
> and now wants to support linux as a bootable device. Currently, some of
> their trade secrets are contained in the driver as opposed to the controller
> firmware, etc., so for now they wish to release a binary-only driver to
> certain beta customers. (i.e., 1st stage of porting is similar functionality
> as windows). Am I correct that in order to boot off of this device that the
> driver would have to be statically linked in vs. a module which could be
> distributed as a binary-only driver keyed to the kernel.revision of the
> distribution's kernel? I would like to avoid any flames and ask that all
> recognize that some hardware providers are having to ease into the pond a toe
> at a time. Any constructive thoughts, suggestions, references, tips, etc.
> highly appreciated.
The driver could be a module and live in initramfs. If you can
get the initial Linux image and initramfs loaded, you would be okay.
The problem is more in the bootloader (LILO or GRUB) would not no how
to do raid. The /boot partition would have to be on a non-raid partition.
Same problem if driver is statically linked in the kernel.
next prev parent reply other threads:[~2003-08-27 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 22:40 joe briggs
2003-08-27 21:57 ` Stephen Hemminger [this message]
2003-08-27 22:17 ` Alan Cox
2003-08-28 12:33 ` joe briggs
2003-08-28 0:22 ` Samuel Flory
2003-08-28 18:32 ` Samuel Flory
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=20030827145755.7e1ce956.shemminger@osdl.org \
--to=shemminger@osdl.org \
--cc=jbriggs@briggsmedia.com \
--cc=linux-kernel@vger.kernel.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®