From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: BACKPACK USB Adapter
Date: Thu, 15 Nov 2001 21:55:42 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100586134201914@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100585571510414@msgid-missing>
On Thu, Nov 15, 2001 at 02:24:56PM -0600, Ken Hahn wrote:
> So I was just on the Linux-USB list and it was recommended I take a
> look over here.
>
> I'm trying to get the Micro Solutions BACKPACK USB adapter supported
> under Linux.
>
> It's a simple mass-storage device, but it needs to have a firmware
> loaded (actually several, but it's a long story). Fxload and hotplug
> sure sound like the trick.
>
> My question:
> What should I be creating?
>
> 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?
I have a few ideas on how this can be done, and have been waiting for
2.5 to start work on it.
Basically, there will be a hotplug-firmware package, possibly split up
into the different device types if it gets too big, and firmware for
devices starts changing too often.
This package will contain the firmware for different devices, and the
program that is used to download the firmware to the devices when they
are plugged in. There is a firmware loader currently in the hotplug
package, and this is a great place to start with. There needs to be
some way to add hooks into the hotplug scripts to look in a specific
location for what devices need firmware sent to them, but that
shouldn't be that tough to do.
If you already have some code and firmware that does this, I'd love to
look at it.
Did that help?
thanks,
greg k-h
_______________________________________________
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
next prev parent reply other threads:[~2001-11-15 21:55 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 [this message]
2001-11-16 0:09 ` David Brownell
2001-11-16 9:31 ` Oliver.Neukum
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-100586134201914@msgid-missing \
--to=greg@kroah.com \
--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).