public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
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 12:20:55 +0100	[thread overview]
Message-ID: <1296818455.19557.11.camel@maggie> (raw)
In-Reply-To: <C038DB15-6427-46CC-A730-1A39CE6B9317@daleenterprise.com> (sfid-20110203_221456_874114_36A0BE2C)

On Thu, 2011-02-03 at 22:14 -0500, Dale Walsh wrote: 
> I see so if I can compile the ssb-sprom program I am able to perform  
> "flashing" of SPROM's on various Broadcom based wireless cards  
> without doing anything else, not likely since the kernel may not have  
> the required support or functionality.
> 
> A kernel compiled without the included dependancies and features  
> doesn't support it and the linux based OS I am familiar with doesn't  
> require rebuilding the kernel to add support or functionality to do  
> anything but is not compatible with the the general linux  
> distributions drivers.
> 
> My opinion is that there shouldn't be any dependent code in the  
> kernel to perform these flashing tasks.
> 
> Finding all the code that relates to the Broadcom wireless device and  
> it's functionality should be inclusive in the b43 code, having to  
> look outside this code to find code that performs the flashing makes  
> no sense and the use of nested abstraction layers and code buried in  
> structs for functionality only makes it difficult for a person not  
> familiar with the code base to locate anything and my opinion is  
> there should be no need to look outside the b43 code.

Wow, it's really funny to read your mail.
That stuff is so clueless and ridiculous... You must be the
master troll.

I do actually remember why I put you into my mailfilters back in 2008.
I did one mistake, however. I later reinstalled the machine and did
not put the filters back.

To say once again what I already said in 2008:
We are not your personal support army for your questionable business.

-- 
Greetings Michael.

  parent reply	other threads:[~2011-02-04 11:20 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 [this message]
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=1296818455.19557.11.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