From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ken Hahn" Date: Thu, 15 Nov 2001 20:24:56 +0000 Subject: BACKPACK USB Adapter MIME-Version: 1 Content-Type: multipart/mixed; boundary="------------InterScan_NT_MIME_Boundary" Message-Id: List-Id: To: linux-hotplug@vger.kernel.org This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----=_NextPart_000_0030_01C16DE1.4CC606C0" ------=_NextPart_000_0030_01C16DE1.4CC606C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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,=20 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? Thanks for any advice? Ken Hahn Engineer, Micro Solutions ------=_NextPart_000_0030_01C16DE1.4CC606C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

So I was just on the Linux-USB list and it was = recommended I=20 take a look over here.

I'm trying to get the Micro Solutions BACKPACK USB = adapter=20 supported under Linux.

It's a simple mass-storage device, but it needs to = have a=20 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=20 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=20 repository of scripts for different devices?

It seems simple enough, and I've got it roughly = working on my=20 machine here,

but how is it going to be easy for the users? I'd = like to have=20 this be easy for people to add to their distributions. Make our = own .deb's=20 and .RPM's???? Is there a previously existent repository=20 package?

Thanks for any advice?

Ken Hahn

Engineer, Micro Solutions

------=_NextPart_000_0030_01C16DE1.4CC606C0-- --------------InterScan_NT_MIME_Boundary-- _______________________________________________ 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