From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: unable to write flashrom, functionality broken?
Date: Tue, 01 Feb 2011 10:28:48 -0600 [thread overview]
Message-ID: <4D4834C0.5060701@lwfinger.net> (raw)
In-Reply-To: <26E2E0F1-1CD4-4A96-B96F-D1F7B6EE5B17@daleenterprise.com>
On 02/01/2011 05:23 AM, Dale Walsh wrote:
> I had a hard drive failure which forced me to perform a fresh/clean
> installation of ubuntu 10 on a new drive since the old drive no longer
> functions (it was rather old).
>
> My use of the b43 software is only for modification of the PCI ID's of
> the flashrom and the original installation was provided to me on the HD.
>
> Now I am unable to write the flashrom after the new installation it
> always reports "write error: Operation Not Supported" and this is using
> the same cards I was flashing before, I even tried using
> a previously modified card and I get the same failure.
>
> Since it worked before I can only conclude that the new software is
> broken and the ability to write is a requirement, can someone help me
> resolve this please.
I do not doubt that the SPROM writing function is broken, but I wonder why you
are needing it now. Why was it necessary to rewrite the SPROM in the first
place? Once that was done, then it should never need to be done again. Please
explain what you did and what you are doing now.
Larry
next prev parent reply other threads:[~2011-02-01 16:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 11:23 unable to write flashrom, functionality broken? Dale Walsh
2011-02-01 12:51 ` Rafał Miłecki
2011-02-01 12:57 ` Ehud Gavron
2011-02-01 16:28 ` Larry Finger [this message]
2011-02-02 7:50 ` Dale Walsh
2011-02-03 3:27 ` Larry Finger
2011-02-03 11:49 ` Dale Walsh
2011-02-03 11:59 ` Michael Büsch
2011-02-03 12:27 ` Dale Walsh
2011-02-03 22:06 ` Michael Büsch
2011-02-03 22:34 ` Peter Stuge
2011-02-03 22:49 ` Michael Büsch
2011-02-03 23:47 ` Peter Stuge
2011-02-04 0:29 ` Michael Büsch
2011-02-04 1:16 ` Peter Stuge
2011-02-04 3:14 ` Dale Walsh
2011-02-04 5:49 ` richardvoigt at gmail.com
2011-02-04 12:06 ` Dale Walsh
2011-02-04 12:21 ` Michael Büsch
2011-02-04 21:38 ` Dale Walsh
2011-02-04 22:22 ` Ehud Gavron
2011-02-04 22:26 ` Michael Büsch
2011-02-04 22:29 ` Rafał Miłecki
2011-02-04 11:20 ` Michael Büsch
2011-02-04 12:17 ` Dale Walsh
2011-02-04 16:55 ` Michael Büsch
2011-02-03 23:36 ` Dale Walsh
2011-02-03 23:49 ` Peter Stuge
2011-02-04 0:17 ` Michael Büsch
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=4D4834C0.5060701@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.