From: "Michael Büsch" <mb@bu3sch.de>
To: b43-dev@lists.infradead.org
Subject: unable to write flashrom, functionality broken?
Date: Fri, 04 Feb 2011 01:17:44 +0100 [thread overview]
Message-ID: <1296778664.9535.36.camel@maggie> (raw)
In-Reply-To: <079FAB8F-1303-41DB-ACC9-D04E284EDDF7@daleenterprise.com> (sfid-20110204_003632_612620_2DB39BC7)
On Thu, 2011-02-03 at 18:36 -0500, Dale Walsh wrote:
> The SPROM writing code itself might not be so bad but the b43 code
> has stuff all over the place and scavenging through all the files
> trying to find the relevant material would require more time that I
> have to get a working solution, not exactly what I'd call cohesive
> when you start looking at code and you have to look all over the
> place to find stuff, my dislike is in the structure or I should state
> lack of.
Claiming a distaste for the spread of code into subsystems and the
lack of structure at the same time is an interesting thing to do...
As I mentioned before: You do not have to dig through all those
files. There are fast and easy to use standard Unix tools that do
this job for you.
> This is not to say that the package as a whole is not good but having
> to rebuild a kernel to add driver support is in my opinion a poor
> design concept, drivers should be standalone and not require
> additional code inserted in the kernel to obtain functionality.
Yeah, and that is why there is absolutely no need to recompile
the kernel, if you want to add a driver. _Especially_ not for wireless.
The Linux wireless developers maintain the compat-wireless package,
which is a major effort for the only purpose of end-user convenience.
> If I could extract the code and generate a standalone app to perform
> the flash it would make it much easier to resolve write issues.
ssb-sprom basically _is_ the standalone app to perform sprom
modification. For the actual "flashing" (it's not flash)
you'll need kernel support, naturally. There's no sane way around
that requirement. The kernel part is tiny, and you will always need it.
> >> I installed ubuntu 10.10 and it works so there is something in the
> >> 10.04 CD ubuntu sent me that causes the failure so for future
> >> reference, you can tell them to upgrade to 10.10 and the failure goes
> >> away.
> >
> > I suggest you report this to the Ubuntu bugzilla.
>
> Report what?
Report that SSB SPROM writing is broken in Ubuntu 10.04, so
that Ubuntu developers can fix it. There's no way I can fix that,
because I am an upstream maintainer. And my upstream code is OK
as of latest revision.
> It's mentioned that the code is messed up
For a proper technical conversation it's always a good idea
to avoid unqualified and unproven claims.
That basically leads nowhere, except for aggressive replies.
--
Greetings Michael.
prev parent reply other threads:[~2011-02-04 0:17 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
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 [this message]
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=1296778664.9535.36.camel@maggie \
--to=mb@bu3sch.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox