From: "Alexander Sychev" <santucco@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Radeon driver
Date: Fri, 20 Oct 2006 18:06:07 +0400 [thread overview]
Message-ID: <op.thp34hhchipq0d@santucco.avp.ru> (raw)
In-Reply-To: <4537378C.9070801@free.fr>
Hi!
That is pity, but it doesn't work :-(.
I have got a "chatoyant" screen with a disappearing kernel output.
The system doesn't react to any commands and I can only poweroff the
laptop.
I'm going to try to get some logs from aux/vga.
On Thu, 19 Oct 2006 12:30:04 +0400, Anel Philippe <xigh@free.fr> wrote:
>
> Hello,
>
> You can download the following required files :
>
> http://xigh.free.fr/radeon.c -> /sys/src/cmd/aux/vga
> http://xigh.free.fr/radeon.h -> /sys/src/cmd/aux/vga
>
> http://xigh.free.fr/vgaradeon.c -> /sys/src/9/pc
>
> http://xigh.free.fr/vgadb -> merge with /lib/vgadb
>
> Please note I couldn't test if this version fully works. Indeed the only
> Radeon chipset I have (for the moment) is in my laptop (XPress 200M)
> and I know for sure it doesn't work (I planned to work on the driver
> but for lack of time, I couldn't). So ... pay carreful attention with
> these
> files (and your computer).
>
> Regards,
> Phil;
>
> Ps: I would suggest you to buy Intel/Nvidia's chipsets whenever you
> can. Indeed newer Ati's chipsets are not documented at all (I don't
> have docs and reading x11 drivers is ... a real drag ...) and only
> commercial drivers work (even for 2D only stuff) ... not to mention
> the fact Nvidia's chipsets seem to be much better designed than
> Ati one's. I mean that regarding api ... in order to add support for
> a newer Nvidia's chipset ... it seems you only have to edit
> /lib/vgadb.
> This not true with Ati.
>
>
--
Best regards,
santucco
next prev parent reply other threads:[~2006-10-20 14:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 13:44 Alexander Sychev
2006-10-18 6:06 ` Philippe Anel
2006-10-18 14:13 ` Alexander Sychev
2006-10-18 14:35 ` Alexander Sychev
2006-10-19 8:30 ` Anel Philippe
2006-10-19 12:23 ` Wes Kussmaul
2006-10-19 20:06 ` Sascha Retzki
2006-10-20 1:02 ` Wes Kussmaul
2006-10-19 12:31 ` erik quanstrom
2006-10-20 14:06 ` Alexander Sychev [this message]
2009-05-29 23:30 Venkatesh Srinivas
2009-06-01 9:14 ` Balwinder S Dheeman
2009-06-01 9:14 ` Balwinder S Dheeman
2009-06-01 19:14 ` Venkatesh Srinivas
2009-06-02 0:54 ` erik quanstrom
2009-06-02 1:18 ` Venkatesh Srinivas
2009-06-02 1:31 ` Ori Bernstein
2009-06-02 14:51 ` erik quanstrom
2009-06-04 19:46 ` erik quanstrom
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=op.thp34hhchipq0d@santucco.avp.ru \
--to=santucco@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).