public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: joe briggs <jbriggs@briggsmedia.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: binary kernel drivers re. hpt370 and redhat
Date: Thu, 28 Aug 2003 08:33:01 -0400	[thread overview]
Message-ID: <200308280833.01136.jbriggs@briggsmedia.com> (raw)
In-Reply-To: <1062022619.23531.38.camel@dhcp23.swansea.linux.org.uk>

I believe that companies will eventually see it costs less and the benefits 
higher to open source their drivers.  But that is a conclusion and paradigm 
that they will have to evolve to themselves, and shoving it down their 
throats will only lengthen the process.  The first step is to support their 
hardware under the platform (linux), and that is what I am focusing on.  

Thanks for the technical analysis and suggestions.

Joe

On Wednesday 27 August 2003 06:17 pm, you wrote:
> On Mer, 2003-08-27 at 22:57, Stephen Hemminger wrote:
> > 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
>
> Standard practice - its not IMHO so much trade secrets as "improving the
> barrier to vendor change" 8). Pretty much all of the older PATA
> controllers don't actually do hardware raid but bios/driver raid - ie
> its the equivalent (or roughly so) of the md layer but locks you into
> the vendor. The notable exception here is the 3ware card (there are a
> couple of others too - Promise Supertrak100, SX6000)
>
> We know some of these formats (eg see the hptraid driver in 2.4.2x)
>
> > 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.
>
> Plus little issues like the GPL 8)

-- 
Joe Briggs
Briggs Media Systems
105 Burnsen Ave.
Manchester NH 01304 USA
TEL 603-232-3115 FAX 603-625-5809 MOBILE 603-493-2386
www.briggsmedia.com

  reply	other threads:[~2003-08-28 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 22:40 binary kernel drivers re. hpt370 and redhat joe briggs
2003-08-27 21:57 ` Stephen Hemminger
2003-08-27 22:17   ` Alan Cox
2003-08-28 12:33     ` joe briggs [this message]
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=200308280833.01136.jbriggs@briggsmedia.com \
    --to=jbriggs@briggsmedia.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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