9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lorenzo Fernando Bivens de la Fuente <lorenzobivens@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Broadcom 4401 driver... Where are you??
Date: Tue, 27 Mar 2007 14:14:15 -0600	[thread overview]
Message-ID: <200703271414.16094.lorenzobivens@gmail.com> (raw)
In-Reply-To: <9ab217670703271200v66bf1db6k1b475a7995df9593@mail.gmail.com>

Devon:

I changed my application a little. I want to work on several NIC drivers, 
4401, 57xx, 43xx (Wireless) and some others... I'd also would like to see if 
it is possible to sync plan 9 drivers with the inferno ones (Uriel 
suggestion). It sounds interesting for me to get an interesting view of the 
two OSs.

On the other hand, hardware support is really important. I'd love to put my 
two cents to help plan 9's hardware support, specially on something 
9essential ;) like NICs.

I've other plans for plan 9 too that suits my necessities, but for the moment, 
let's make it work ;)

I really appreciate any kind of comments, suggestions, "pushing" or help.

Cheers!


On Tuesday 27 March 2007 13:00:37 Devon H. O'Dell wrote:
> 2007/3/27, Lorenzo Fernando Bivens de la Fuente <lorenzobivens@gmail.com>:
> > On Tuesday 27 March 2007 12:28:27 geoff@plan9.bell-labs.com wrote:
> > > I'm not aware of a working broadcom driver.  If there is one, we'd
> > > like to have it too.
> > >
> > > There is a started but not finished broadcom driver that several
> > > people have.
> >
> > Again, everybody talks about it, but I haven't seen it... the only
> > broadcom driver I've seen is for a 57xx something series...
> >
> > cheers!
>
> Hey Lorenzo,
>
> The details are as follows. There was talk of a 4401 driver -- ericvh
> said that jmk had a mostly working version -- on the mentor comments
> of your SoC application. The stuff Uriel posted there was for the 57xx
> ServerWorks chipset.
>
> I have documentation for all the 57xx chips, so I can help you with
> that implementation. As far as the 4401, I don't have docs, but I've
> perused other drivers. If you aren't interested in a 57xx driver, I'm
> sure I can get one done at some point.
>
> I do see that you were assigned a mentor for another project to which
> you applied. If you are accepted, do you have a preference for which
> project you work on?
>
> --Devon




      reply	other threads:[~2007-03-27 20:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27  6:44 Lorenzo Fernando Bivens de la Fuente
2007-03-27 18:28 ` geoff
2007-03-27 18:36   ` Lorenzo Fernando Bivens de la Fuente
2007-03-27 19:00     ` Steve Simon
2007-03-27 19:05       ` Devon H. O'Dell
2007-03-27 19:00     ` Devon H. O'Dell
2007-03-27 20:14       ` Lorenzo Fernando Bivens de la Fuente [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=200703271414.16094.lorenzobivens@gmail.com \
    --to=lorenzobivens@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).