From: Philippe Anel <xigh@free.fr>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Broadcom drivers, yet again
Date: Mon, 22 Oct 2007 16:41:26 +0200 [thread overview]
Message-ID: <471CB696.9070607@free.fr> (raw)
In-Reply-To: <6e35c0620710220710y6ea2201brbe989abf58d055e@mail.gmail.com>
I see what you mean, Jack. Thanks to virtualization, this is no longer a
problem. Newbies can
deal with Vmware or Qemu.
Regarding the fact vendors change their chipsets very often, I agree
with you, this is a very
anoying problem (especially with notebooks).
The fact is you cannot say precisely on which hardware plan9 will work,
because specs
are changing quicly.
However, there is only a few things to know :
- Some SATA chipsets are now supported thanks to Erik, but you still
cannot install
plan9 to SATA devices because 9load has not been recompiled to do so
(yet).
- Only UHCI Usb controlers are supported, which means you can forget
AMD/ATI
chipset if you have to deal with usb devices (other than kbd or mouse).
- Thanks to VESA support, almost all graphic cards are working
(except you can have
some freezes because realmode doesn't work well with mp).
- Realtek and Intel networking controller are working quite well
(sometimes you have
to add pci ids to the sources).
Phil;
Jack Johnson a écrit :
> Newbies have an expectation, even with non-commercial software now,
> that they can take a random box, pop in a CD, and if they have any
> problems it's likely that their display looks like crap and they can't
> print (think Linux or Vista). What might be helpful for our newbies
> is to say something like hey, a Dell GX1 through GX260 should work off
> the shelf, or an HP/Compaq models L through X but not V, no Sonys,
> whatever. Give everyone some arbitrary measure so when they're
> eyeballing a workstation at the store or in the garage or wherever
> they don't have to boot it to find out what the integrated chipset is
> and whether or not it's supported.
>
> The wiki used to do a better job in this regard, but the problem is a
> wooden boat. Too many models, user pool is too small, vendors change
> their chipsets with their underwear. But, users tend to have just two
> questions in this arena: will this work with my hardware, or what
> should I buy/find to work with Plan 9?
>
> It would probably be easiest to just say it up front:
>
> "Will Plan 9 work with my hardware?"
> "Probably not all of it. But, your mind only works with 10% of your
> brain, so it's not a big deal."
> "What hardware should I buy to work with Plan 9?"
> "...NIC: Intel PRO/100 or PRO/1000..."
> "Hey, I have that already!"
> "You just saved $40."
>
> -Jack
>
>
>
next prev parent reply other threads:[~2007-10-22 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 12:33 Pietro Gagliardi
2007-10-21 12:44 ` erik quanstrom
2007-10-21 13:34 ` Pietro Gagliardi
2007-10-21 13:55 ` erik quanstrom
2007-10-21 14:03 ` Steve Simon
2007-10-21 14:06 ` erik quanstrom
2007-10-21 14:24 ` Pietro Gagliardi
2007-10-21 14:30 ` erik quanstrom
2007-10-21 14:35 ` Pietro Gagliardi
2007-10-21 15:51 ` Jack Johnson
2007-10-22 7:32 ` Philippe Anel
2007-10-22 14:10 ` Jack Johnson
2007-10-22 14:23 ` ron minnich
2007-10-22 14:45 ` erik quanstrom
2007-10-22 14:41 ` Philippe Anel [this message]
2007-10-22 14:59 ` erik quanstrom
2007-10-22 15:04 ` Philippe Anel
2007-10-24 10:41 ` Richard Miller
2007-10-24 12:32 ` erik quanstrom
2007-10-24 13:27 ` Philippe Anel
2007-10-26 8:34 ` Richard Miller
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=471CB696.9070607@free.fr \
--to=xigh@free.fr \
--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).