From: Dave <kilroyd@googlemail.com>
To: linux-kernel@vger.kernel.org
Cc: dwmw2@infradead.org, orinoco-users@lists.sourceforge.net
Subject: linux-firmware binary corruption with gitweb
Date: Sat, 28 Feb 2009 19:24:26 +0000 [thread overview]
Message-ID: <49A98F6A.50702@gmail.com> (raw)
I'm aware of at least a couple users of orinoco who have picked up
corrupt firmware# from the linux-firmware tree*.
I've verified that the firmware in the repository itself is correct.
It appears that downloading the file using the blob/raw links from
gitweb causes the corruption (0xc3 everywhere). At least it does with
firefox.
Is this known/expected behaviour?
Thanks,
Dave.
#<http://marc.info/?l=orinoco-users&m=123411762524637>
*<http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=shortlog>
next reply other threads:[~2009-02-28 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 19:24 Dave [this message]
2009-03-01 5:47 ` [Orinoco-users] linux-firmware binary corruption with gitweb Pavel Roskin
2009-03-03 18:59 ` Dave
2009-03-04 0:26 ` Jakub Narebski
2009-03-04 23:52 ` Dave
2009-03-05 17:26 ` Pavel Roskin
2009-03-06 0:03 ` Jakub Narebski
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=49A98F6A.50702@gmail.com \
--to=kilroyd@googlemail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orinoco-users@lists.sourceforge.net \
/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).