unable to write flashrom, functionality broken?

Peter Stuge peter at stuge.se
Thu Feb 3 20:16:20 EST 2011

Michael Büsch wrote:
> To understand the ssb_sprom file, you do _not_ have to read one
> single line of sysfs code.

Of course. But it can be important to know what sysfs is and what
patterns it uses in order to see a bigger picture.

> To understand the whole SSB SPROM writing, you have to read about
> 200 lines of code.


> > It's not at all obvious to a newcomer where the kernel edge is,
> > or even that the kernel is so distinct.
> Why would a newcomer who doesn't even know what an operating system
> kernel is

That's not what I wrote though. I agree with you that it's important
to try to be as accurate as possible.

By "the kernel" I mean Linux. Someone working expertly with a
completely different system may think in the (simplistic) term
Ubuntu. It's a long way from that high-level view into the file with
code that writes the SPROM.

> want to write an SSB SPROM?

As was explained, in this case a Ubuntu system was used as a tool in
a production process.

> That guy will brick his device anyway, as he _will_ write incorrect
> data to the SPROM.

I think it's possible to find a person who knows nearly every bit in
the SPROM, but who knows nothing about Linux. I don't think there's
correlation between the two.

> The next thing you'll probably blame on me is that I did not
> document in the b43 documentation how to use a qwerty keyboard.

I have not and do not blame anything on you.

I think you're being much too sensitive about what I wrote. It was
clear (to me) that you snapped into defensive mode, and that's
unfortunate since I do not believe anyone was attacking you.
(I.e. saying something like Martin is stupid, Martin writes bad code,
or it's Martin's fault that this code does not work on this Ubuntu
version. I certainly don't suggest any of that.)

I don't think that it's your fault that Linux systems are sometimes
complex beasts.. :)


More information about the b43-dev mailing list