From: Olivier Galibert <galibert@pobox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac14
Date: Wed, 23 May 2001 05:36:20 -0400 [thread overview]
Message-ID: <20010523053620.C7114@zalem.puupuu.org> (raw)
In-Reply-To: <Pine.LNX.4.05.10105230915100.16280-100000@callisto.of.borg> <20677.990608858@kao2.melbourne.sgi.com>
In-Reply-To: <20677.990608858@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Wed, May 23, 2001 at 07:07:38PM +1000
On Wed, May 23, 2001 at 07:07:38PM +1000, Keith Owens wrote:
> On Wed, 23 May 2001 09:17:08 +0200 (CEST),
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >On Wed, 23 May 2001, Keith Owens wrote:
> >> Is drivers/char/ser_a2232fw.ax supposed to be included? Nothing uses it.
> >
> >It's the source for the firmware hexdump in ser_a2232fw.h, provided as a
> >reference.
>
> What is the point of including it in the kernel source tree without the
> code to convert it to ser_a2232fw.h? Nobody can use ser_a2232fw.ax, it
> is just bloat.
We don't provide the binutils or gcc with the kernel either. The 6502
is a rather well known processor. Try plonking "6502 assembler" in
google and you'll have a lot of choice.
Having the source with the .h helps doing this little thing called
debugging.
OG, who hates acenic_firmware.h for that exact same reason.
next prev parent reply other threads:[~2001-05-23 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 14:45 Linux 2.4.4-ac13 Alan Cox
2001-05-22 21:30 ` Linux 2.4.4-ac14 Alan Cox
2001-05-22 22:09 ` Linux 2.4.4-ac13 Francois Romieu
2001-05-23 2:05 ` Linux 2.4.4-ac14 Keith Owens
2001-05-23 7:17 ` Geert Uytterhoeven
2001-05-23 9:07 ` Keith Owens
2001-05-23 9:36 ` Olivier Galibert [this message]
2001-05-23 10:03 ` Keith Owens
2001-05-23 16:42 ` Geert Uytterhoeven
2001-05-23 10:08 ` David Weinehall
2001-05-24 17:43 ` Thomas Dodd
2001-05-23 9:07 ` Alan Cox
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=20010523053620.C7114@zalem.puupuu.org \
--to=galibert@pobox.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®