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:29:05 +0100 [thread overview]
Message-ID: <1296779345.9535.46.camel@maggie> (raw)
In-Reply-To: <20110203234730.28953.qmail@stuge.se> (sfid-20110204_004735_721902_FFFFFFFFD8BEB068)
On Fri, 2011-02-04 at 00:47 +0100, Peter Stuge wrote:
> > You're simply unaware of the basic Unix tools that help you find
> > what you are searching for.
>
> Not at all. If I was the one looking for the code that talks to
> hardware I'd not only know where to find it, but I'd also know every
> other component of hardware and software that the data passes through
> on the way.
A basic thing about software abstraction is that you do _not_ need
to know what a subsystem does internally. To understand the ssb_sprom
file, you do _not_ have to read one single line of sysfs code.
To understand the whole SSB SPROM writing, you have to read about 200
lines of code.
> > Luckily the tool to find something is called "find".
>
> I think you may have missed my point. One part is certainly to know
> how to find a file in a Linux system, but more important is the
> question of what to search for (a file) and where to search (in the
> kernel codebase). It's not at all obvious to a newcomer where the
> kernel edge is, or even that the kernel is so distinct.
I think we're probably drifting offtopic. Why would a newcomer who
doesn't even know what an operating system kernel is want to
write an SSB SPROM? That guy will brick his device anyway, as
he _will_ write incorrect data to the SPROM.
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.
--
Greetings Michael.
next prev parent reply other threads:[~2011-02-04 0:29 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 [this message]
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=1296779345.9535.46.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;
as well as URLs for NNTP newsgroup(s).