From: Marcel Holtmann <marcel@holtmann.org>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Jan Harkes <jaharkes@cs.cmu.edu>, Greg KH <greg@kroah.com>,
Sven Luther <sven.luther@wanadoo.fr>,
Michael Poole <mdpoole@troilus.org>,
debian-legal@lists.debian.org, debian-kernel@lists.debian.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/04] Load keyspan firmware with hotplug
Date: Tue, 05 Apr 2005 11:22:06 +0200 [thread overview]
Message-ID: <1112692926.8263.125.camel@pegasus> (raw)
In-Reply-To: <200504042351.22099.dtor_core@ameritech.net>
Hi Jan,
> > > > Mmm, probably that 2001 discussion about the keyspan firmware, right ?
> > > >
> > > > http://lists.debian.org/debian-legal/2001/04/msg00145.html
> > > >
> > > > Can you summarize the conclusion of the thread, or what you did get from it,
> > > > please ?
> > >
> > > That people didn't like the inclusion of firmware, I posted how you can
> > > fix it by moving it outside of the kernel, and asked for patches.
> > >
> > > None have come.
> >
> > Didn't know you were waiting for it. How about something like the
> > following series of patches?
> >
> > [01/04] - add simple Intel IHEX format parser to the firmware loader.
>
> Firmware loader is format-agnostic, I think having IHEX parser in a separate
> file would be better...
I agree with Dmitry on this point. The IHEX parser should not be inside
firmware_class.c. What about using keyspan_ihex.[ch] for it?
Regards
Marcel
next prev parent reply other threads:[~2005-04-05 9:23 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 10:09 non-free firmware in kernel modules, aggregation and unclear copyright notice Sven Luther
2005-04-04 10:21 ` Arjan van de Ven
2005-04-04 10:59 ` Sven Luther
2005-04-07 7:17 ` Jes Sorensen
2005-04-07 11:27 ` Sven Luther
2005-04-04 13:26 ` Michael Poole
2005-04-04 14:16 ` Sven Luther
2005-04-04 17:51 ` Greg KH
2005-04-04 18:21 ` Sven Luther
2005-04-04 19:12 ` Ian Campbell
2005-04-04 19:24 ` Sven Luther
2005-04-04 19:36 ` Roland Dreier
2005-04-04 18:27 ` Sven Luther
2005-04-04 19:17 ` Greg KH
2005-04-04 19:29 ` Sven Luther
2005-04-04 19:58 ` Adrian Bunk
2005-04-04 20:23 ` Sven Luther
2005-04-04 21:05 ` Adrian Bunk
2005-04-04 21:16 ` Sven Luther
2005-04-04 20:55 ` Theodore Ts'o
2005-04-04 21:19 ` Sven Luther
2005-04-05 8:19 ` Ian Campbell
2005-04-05 8:32 ` Sven Luther
2005-04-05 8:49 ` Ian Campbell
2005-04-05 9:11 ` Christoph Hellwig
2005-04-05 9:28 ` Arjan van de Ven
2005-04-05 9:32 ` Christoph Hellwig
2005-04-05 9:36 ` Arjan van de Ven
2005-04-05 9:39 ` Christoph Hellwig
2005-04-05 10:42 ` Andres Salomon
2005-04-05 9:46 ` Sven Luther
2005-04-05 12:09 ` Jeff Garzik
2005-04-05 12:14 ` Arjan van de Ven
2005-04-06 19:22 ` Eric W. Biederman
2005-04-07 9:34 ` Jeff Garzik
2005-04-07 10:28 ` Christoph Hellwig
2005-04-07 11:27 ` Sven Luther
2005-04-07 11:46 ` Eric W. Biederman
2005-04-07 18:42 ` Sven Luther
2005-04-08 3:06 ` Eric W. Biederman
2005-04-08 6:41 ` Sven Luther
2005-04-05 9:30 ` Ian Campbell
2005-04-05 9:36 ` Sven Luther
2005-04-05 15:21 ` Sven Luther
2005-04-05 21:37 ` Don Armstrong
2005-04-05 4:23 ` [PATCH 00/04] Load keyspan firmware with hotplug Jan Harkes
2005-04-05 4:26 ` [PATCH 01/04] " Jan Harkes
2005-04-05 4:27 ` [PATCH 02/04] " Jan Harkes
2005-04-05 4:28 ` [PATCH 03/04] " Jan Harkes
2005-04-05 4:51 ` [PATCH 00/04] " Dmitry Torokhov
2005-04-05 8:32 ` Kay Sievers
2005-04-05 11:39 ` Jan Harkes
2005-04-05 9:22 ` Marcel Holtmann [this message]
2005-04-05 11:45 ` Jan Harkes
2005-04-05 14:36 ` Marcel Holtmann
2005-04-05 15:28 ` Dmitry Torokhov
2005-04-05 15:37 ` Marcel Holtmann
2005-04-05 15:31 ` Jan Harkes
2005-04-05 16:46 ` Marcel Holtmann
2005-04-05 16:20 ` Dmitry Torokhov
2005-04-05 5:36 ` Sven Luther
2005-04-04 18:39 ` non-free firmware in kernel modules, aggregation and unclear copyright notice Matthew Wilcox
2005-04-04 19:55 ` Jeff Garzik
2005-04-04 20:27 ` Sven Luther
2005-04-04 20:47 ` Jeff Garzik
2005-04-04 21:24 ` Sven Luther
2005-04-04 21:58 ` Sven Luther
2005-04-05 9:33 ` Sven Luther
2005-04-07 1:05 ` Alan Cox
2005-04-07 7:28 ` Jes Sorensen
2005-04-07 7:25 ` Jes Sorensen
2005-04-07 8:04 ` David Schmitt
2005-04-07 8:17 ` Xavier Bestel
2005-04-07 8:32 ` Olivier Galibert
2005-04-07 8:46 ` Xavier Bestel
2005-04-07 8:26 ` David Schwartz
2005-04-07 20:16 ` Raul Miller
2005-04-07 23:20 ` David Schwartz
2005-04-08 3:55 ` Raul Miller
2005-04-08 7:41 ` Sven Luther
2005-04-08 12:30 ` Raul Miller
2005-04-04 19:05 ` Marco d'Itri
2005-04-04 19:14 ` Greg KH
2005-04-04 19:32 ` Adrian Bunk
2005-04-05 14:05 ` Josselin Mouette
2005-04-05 15:39 ` Sven Luther
2005-04-07 21:07 ` Adrian Bunk
2005-04-08 7:22 ` Josselin Mouette
2005-04-08 11:23 ` Jörn Engel
2005-04-08 17:34 ` Adrian Bunk
2005-04-08 17:42 ` Josselin Mouette
2005-04-08 18:01 ` Adrian Bunk
2005-04-08 18:16 ` Rich Walker
2005-04-08 18:42 ` Josselin Mouette
2005-04-10 9:24 ` Giuseppe Bilotta
2005-04-11 20:55 ` Raul Miller
2005-04-09 0:31 ` Raul Miller
2005-04-09 14:38 ` Adrian Bunk
2005-04-09 20:31 ` Raul Miller
2005-04-08 11:53 ` Sven Luther
2005-04-04 19:41 ` Sven Luther
[not found] <psd40B.A.hYG.lSiUCB@murphy>
2005-04-05 15:12 ` [PATCH 00/04] Load keyspan firmware with hotplug Humberto Massa
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=1112692926.8263.125.camel@pegasus \
--to=marcel@holtmann.org \
--cc=debian-kernel@lists.debian.org \
--cc=debian-legal@lists.debian.org \
--cc=dtor_core@ameritech.net \
--cc=greg@kroah.com \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mdpoole@troilus.org \
--cc=sven.luther@wanadoo.fr \
/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