From: Oliver Neukum <oliver@neukum.org>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: linux-kernel@vger.kernel.org,
ipw2100-devel@lists.sourceforge.net, smiler@lanil.mine.nu
Subject: Re: [2.6.10-rc1-mm2] Firmware loader gone bogus?
Date: Mon, 1 Nov 2004 01:34:19 +0100 [thread overview]
Message-ID: <200411010134.19922.oliver@neukum.org> (raw)
In-Reply-To: <200410311627.02116.shawn.starr@rogers.com>
Am Sonntag, 31. Oktober 2004 22:27 schrieb Shawn Starr:
> Yeah I noticed my ipw2200 firmware broke in 2.6.10-rc1-bk5
>
> Does 2.6.10-rc1 non-bk snapshots work for you?
Which script do you use to load the firmware?
Regards
Oliver
next prev parent reply other threads:[~2004-11-01 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 21:27 [2.6.10-rc1-mm2] Firmware loader gone bogus? Shawn Starr
2004-11-01 0:34 ` Oliver Neukum [this message]
2004-11-01 0:49 ` Marcel Holtmann
2004-11-01 1:50 ` Shawn Starr
2004-11-01 2:34 ` [Ipw2100-devel] " Shawn Starr
2004-11-01 16:40 ` Christian Axelsson
-- strict thread matches above, loose matches on Subject: below --
2004-10-31 19:51 Christian Axelsson
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=200411010134.19922.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.com \
--cc=smiler@lanil.mine.nu \
/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