From: <Oliver.Neukum@lrz.uni-muenchen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: BACKPACK USB Adapter
Date: Fri, 16 Nov 2001 09:31:28 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100590327030868@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100585571510414@msgid-missing>
> Should I create a script for people to add the correct files in the right places for hotplug to get at, or should I be working to get firmwares to you folk so that it will be in the hotplug package?
> Perhaps there's another package that's going to be the repository of scripts for different devices?
>
> It seems simple enough, and I've got it roughly working on my machine here,
> but how is it going to be easy for the users? I'd like to have this be easy for people to add to their distributions. Make our own .deb's and .RPM's???? Is there a previously existent repository package?
IMHO the hotplug packages should not grow to the point of containing every
firmware on the planet. Perhaps you should write a patch to the utilities
which will cause them to look for a firmware named after the vendor:device
ids and distribute the firmware seperately, preferrably as an rpm (LSB)
Regards
Oliver
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-11-16 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 20:24 BACKPACK USB Adapter Ken Hahn
2001-11-15 21:55 ` Greg KH
2001-11-16 0:09 ` David Brownell
2001-11-16 9:31 ` Oliver.Neukum [this message]
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=marc-linux-hotplug-100590327030868@msgid-missing \
--to=oliver.neukum@lrz.uni-muenchen.de \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).