From: Jes Sorensen <jes@trained-monkey.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: hiren_mehta@agilent.com ("MEHTA,HIREN (A-SanJose,ex1)"),
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: releasing driver to kernel in source+binary format
Date: 23 Aug 2001 16:14:38 -0400 [thread overview]
Message-ID: <m3vgjelej5.fsf@trained-monkey.org> (raw)
In-Reply-To: <E15ZzmR-0004O1-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Thu, 23 Aug 2001 20:04:39 +0100 (BST)"
>>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> Well, Qlogic also has their firmware released in binary format.
Alan> Firmware that runs on the processor in the card is somewhat of a
Alan> different item. If its just a binary firmware image to load into
Alan> the card and that is run by the card I dont think its an issue.
Alan> If its code run on the host processor then there is an issue.
One might even want to add that opening up firmware has some positive
side effects: Look at how Alteon completely ruled the Gigabit Ethernet
world with their NIC and open firmware programme (until they decided
to bug out before the big players started picking up and squeezing
them out on price).
Jes
next prev parent reply other threads:[~2001-08-23 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 18:43 releasing driver to kernel in source+binary format MEHTA,HIREN (A-SanJose,ex1)
2001-08-23 19:04 ` Alan Cox
2001-08-23 20:14 ` Jes Sorensen [this message]
2001-08-23 19:40 ` Matti Aarnio
-- strict thread matches above, loose matches on Subject: below --
2001-08-23 17:59 MEHTA,HIREN (A-SanJose,ex1)
2001-08-23 18:14 ` Alan Cox
2001-08-23 18:16 ` Ignacio Vazquez-Abrams
2001-08-23 18:26 ` Disconnect
2001-08-24 2:14 ` Steve Underwood
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=m3vgjelej5.fsf@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hiren_mehta@agilent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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