From: Matti Aarnio <matti.aarnio@zmailer.org>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: yacc dependency of aic7xxx driver
Date: Wed, 7 Mar 2001 18:12:27 +0200 [thread overview]
Message-ID: <20010307181227.H23336@mea-ext.zmailer.org> (raw)
In-Reply-To: <200103071442.PAA14348@ns.caldera.de> <200103071529.f27FTjO26978@aslan.scsiguy.com>
In-Reply-To: <200103071529.f27FTjO26978@aslan.scsiguy.com>; from gibbs@scsiguy.com on Wed, Mar 07, 2001 at 08:29:45AM -0700
On Wed, Mar 07, 2001 at 08:29:45AM -0700, Justin T. Gibbs wrote:
> >What about simply removing the firmware source and assembler from the
> >kernel tree? We have lots of firmware in the kernel tree for which
> >there isn't even firmware avaible...
>
> What, and not allow others to fix my bugs for me? :-)
>
> Lots of people have embedded this driver just because it is completely
> open source. I'd like to have all distributions be "complete"
> distributions.
I presume the aicasm (or whatever) can do its meager DB needs
by simpler ubiquitous things like GDBM. SleepyCat DBx is good,
but in this case as serious overkill as e.g. using Oracle ;)
(No, I didn't read the source of the aicasm.)
There really should be some convenient way to compile the firmware
from source when wanted, but the normal case should not be dependent
of FIRMWARE SOURCE - the integer/byte array include file should
be enough for normal users.
$ (cd drivers/xx/yy; make aic7xxx.fw )
What HOSTCC et.al. settings are needed, that I can't say,
and that 'make' method doesn't get top-level definitions in...
Simultaneously (as 'aic7xxx.fw' would not be the real filename),
aic7xxx.o file's dependencies would contain the real firmware
files so that "make bzImage" will recompile it correctly.
When people like Justin are sending the driver update to Linus,
they just need to be carefull at sending all relevant files/diffs.
We are placing a lot of trust to these firmware makers to supply
us working firmware, why not trust them to do it right so that
compiling kernel won't need to generate firmware assembler program
at first...
> --
> Justin
/Matti Aarnio
next prev parent reply other threads:[~2001-03-07 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 11:48 Jörn Nettingsmeier
2001-03-07 14:06 ` Justin T. Gibbs
2001-03-07 14:42 ` Christoph Hellwig
2001-03-07 15:29 ` Justin T. Gibbs
2001-03-07 15:52 ` Richard B. Johnson
2001-03-07 16:12 ` Matti Aarnio [this message]
2001-03-07 18:54 ` Justin T. Gibbs
2001-03-07 16:46 ` Christoph Hellwig
2001-03-07 15:44 ` Jörn Nettingsmeier
2001-03-08 2:34 ` Peter Samuelson
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=20010307181227.H23336@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=gibbs@scsiguy.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®