From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Broadcom driver discussion [Was: Re: [9fans] Is IBM ThinkPad R60e notebook compatible with Plan9?]
Date: Fri, 11 May 2007 09:45:58 -0400 [thread overview]
Message-ID: <9ab217670705110645i2ffc4a8fyd5320a20086c6d7b@mail.gmail.com> (raw)
In-Reply-To: <5d375e920705102257x4a7107d4qfef709af58762e43@mail.gmail.com>
Uriel. You're spouting about things you know nothing about. As usual.
The broadcom code that you have there is simply a compilation of
sources and compiled sources for various non-Plan 9 platforms, like I
told you the first time you posted it. The Plan 9 stuff in there was
too minimal to be useful. The BCM44xx is NOTHING like the ServerWorks
57xx chipsets. It's a different driver. And can everybody just fucking
stop with the FUD? PLEASE? In all these threads?
I'm helping quanstro out with getting documentation and getting
something out there. Come on, people, this isn't high school drama.
Also, Uriel. Please see archives regarding my AC'97 post. There are
many benefits to the CMU AC'97 driver that the one Aki wrote doesn't
have. Take some lithium for Heaven's sake before you have a stroke.
--dho
next prev parent reply other threads:[~2007-05-11 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 4:58 Vester Thacker
2007-05-11 5:02 ` Lorenzo Fernando Bivens de la Fuente
2007-05-11 5:09 ` [9fans] Re: Broadcom driver discussion Lyndon Nerenberg
2007-05-11 5:16 ` Uriel
2007-05-11 5:35 ` Broadcom driver discussion [Was: Re: [9fans] Is IBM ThinkPad R60e notebook compatible with Plan9?] Uriel
2007-05-11 5:39 ` Lyndon Nerenberg
2007-05-11 5:57 ` Uriel
2007-05-11 13:45 ` Devon H. O'Dell [this message]
2007-05-12 0:13 ` Vester Thacker
2007-05-12 4:22 ` Broadcom driver discussion [Was: Re: [9fans] Is IBM ThinkPad R60e lucio
2007-05-12 4:40 ` matt
2007-05-12 14:32 ` lucio
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=9ab217670705110645i2ffc4a8fyd5320a20086c6d7b@mail.gmail.com \
--to=devon.odell@gmail.com \
--cc=9fans@cse.psu.edu \
/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).