From: Stephen Williams <steve@icarus.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug and USB device removal
Date: Sat, 19 May 2001 14:09:48 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99028147413925@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99023795831169@msgid-missing>
bhards@bigpond.net.au said:
> The Keil toolchain eventually ends up with Intel hex as well.
It can also make S-Records, if I recall correctly. Anyhow, it should
work with what I have.
Adam's format includes not just the bytes and addresses, but the 0xa0
of the commands as well. I suspect he didn't quite understand the
workings of the ez-usb chip (he said as much on the linux-usb-devel
mailing list) so may have thought that it was information.
bhards@bigpond.net.au said:
> I remember you said that you needed to clean it up first
Pretty much done. Here's a snapshot:
<ftp://icarus.com/pub/steve/gflashd.tgz>
At the moment it is part of my gflash product, but if it finds a different
home I'll maintain it wherever it lives.
--
Steve Williams "The woods are lovely, dark and deep.
steve@icarus.com But I have promises to keep,
steve@picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-05-19 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 2:05 Hotplug and USB device removal Stephen Williams
2001-05-19 3:13 ` Brad Hards
2001-05-19 4:54 ` Stephen Williams
2001-05-19 10:17 ` Brad Hards
2001-05-19 10:31 ` Brad Hards
2001-05-19 14:09 ` Stephen Williams [this message]
2001-05-19 14:13 ` Stephen Williams
2001-05-19 15:57 ` David Brownell
2001-05-19 20:45 ` Greg KH
2001-05-19 21:33 ` Stephen Williams
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-99028147413925@msgid-missing \
--to=steve@icarus.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).