* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 13:58 ` [9fans] vgaradeon (was Re: Problem of last update?) Venkatesh Srinivas
@ 2010-01-27 14:10 ` erik quanstrom
2010-01-27 17:36 ` geoff
` (2 subsequent siblings)
3 siblings, 0 replies; 19+ messages in thread
From: erik quanstrom @ 2010-01-27 14:10 UTC (permalink / raw)
To: 9fans
> On 1/19, the Radeon driver made it into the Plan 9 distribution; anyone with
> a Radeon R100 (7000, 7500, Mobility M6, M7), some R200 (8500, 9000) or
> some R300s (9500, 9700) is encouraged to try them out, see if they feel faster
> or work for you or whatnot.
>
> The driver also has, disabled-by-default, hardware-accelerated fill and scroll
> routines. If you wish to try them out, modify /sys/src/9/pc/vgaradeon.c to define
> HW_ACCEL; I'd like to hear if they work on your card and if you can feel any
> difference.
>
> In the short term future, I hope to test the driver on a number of other cards
> and add some PCI IDs/anything-else-needed, such as the R9600, 9800, and 9200/9250.
> Longer-term, my goal is always support for more cards.
haven't gotten it to work with "atom" bios on the sb600
integrated chipset.
- erik
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 13:58 ` [9fans] vgaradeon (was Re: Problem of last update?) Venkatesh Srinivas
2010-01-27 14:10 ` erik quanstrom
@ 2010-01-27 17:36 ` geoff
2010-01-27 18:09 ` erik quanstrom
` (3 more replies)
2010-01-28 4:09 ` arpunk
2010-01-28 4:21 ` arpunk
3 siblings, 4 replies; 19+ messages in thread
From: geoff @ 2010-01-27 17:36 UTC (permalink / raw)
To: 9fans
Remember that, on the pc, you should always be able to revert to
monitor=vesa and indeed aux/vga attempts that if it can't recognise
your graphics controller, but it can fail if you're trying to use a
non-vesa resolution. It even works on multiprocessors now.
aux/vga -m vesa -p >/tmp/vesa
will generate a list of acceptable vesa modes, including resolutions,
in /tmp/vesa. The redirection is necessary to avoid interacting with
the vga subsystem while dumping it.
My long-term goal is to eliminate all the vga drivers but vgavesa,
which make up about 10% of the pc kernel port by line count. This may
not be possible due to currently-working graphics cards with broken
vesa bioses nor desirable because the native drivers are vastly faster
than the vesa driver (though I think we're closing that gap), but it's
worth attempting. I've used the vesa driver on my usual plan 9
terminals and it's hard to see a difference in performance compared
with the native vga drivers.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 17:36 ` geoff
@ 2010-01-27 18:09 ` erik quanstrom
2010-01-27 19:02 ` Francisco J Ballesteros
2010-01-27 19:11 ` geoff
` (2 subsequent siblings)
3 siblings, 1 reply; 19+ messages in thread
From: erik quanstrom @ 2010-01-27 18:09 UTC (permalink / raw)
To: 9fans
> My long-term goal is to eliminate all the vga drivers but vgavesa,
> which make up about 10% of the pc kernel port by line count. This may
> not be possible due to currently-working graphics cards with broken
> vesa bioses nor desirable because the native drivers are vastly faster
> than the vesa driver (though I think we're closing that gap), but it's
> worth attempting. I've used the vesa driver on my usual plan 9
> terminals and it's hard to see a difference in performance compared
> with the native vga drivers.
this is a great goal.
unfortunately, some of the machines i happen to have
have awful performance with the vesa driver. in particular,
a scrolling window on my amd sb600 machine will essentially
lock up the machine. you can't use the mouse to kill the
window. :-(. the nvidia driver (for different hardware
in the same machine) performs much better with a bargin
bin card.
also, is it possible to support resolutions greater than
1600x1200x16 with vesa?
- erik
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 18:09 ` erik quanstrom
@ 2010-01-27 19:02 ` Francisco J Ballesteros
0 siblings, 0 replies; 19+ messages in thread
From: Francisco J Ballesteros @ 2010-01-27 19:02 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
In parallels I have 1920x... using the vesa driver.
On Wed, Jan 27, 2010 at 7:09 PM, erik quanstrom <quanstro@coraid.com> wrote:
>> My long-term goal is to eliminate all the vga drivers but vgavesa,
>> which make up about 10% of the pc kernel port by line count. This may
>> not be possible due to currently-working graphics cards with broken
>> vesa bioses nor desirable because the native drivers are vastly faster
>> than the vesa driver (though I think we're closing that gap), but it's
>> worth attempting. I've used the vesa driver on my usual plan 9
>> terminals and it's hard to see a difference in performance compared
>> with the native vga drivers.
>
> this is a great goal.
>
> unfortunately, some of the machines i happen to have
> have awful performance with the vesa driver. in particular,
> a scrolling window on my amd sb600 machine will essentially
> lock up the machine. you can't use the mouse to kill the
> window. :-(. the nvidia driver (for different hardware
> in the same machine) performs much better with a bargin
> bin card.
>
> also, is it possible to support resolutions greater than
> 1600x1200x16 with vesa?
>
> - erik
>
>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 17:36 ` geoff
2010-01-27 18:09 ` erik quanstrom
@ 2010-01-27 19:11 ` geoff
2010-01-27 23:30 ` Gorka Guardiola
2010-01-28 9:34 ` Pavel Klinkovsky
3 siblings, 0 replies; 19+ messages in thread
From: geoff @ 2010-01-27 19:11 UTC (permalink / raw)
To: 9fans
These drivers appear to be for pre-pci ([e]isa or vlb) vga cards:
vgaark2000pv.c
vgact65545.c
vgaet4000.c
I think that these are excellent candidates for removal. Are any of
you still using these drivers? If so, could you try using
monitor=vesa instead and see if that's acceptable, and let me know
privately either way.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 17:36 ` geoff
2010-01-27 18:09 ` erik quanstrom
2010-01-27 19:11 ` geoff
@ 2010-01-27 23:30 ` Gorka Guardiola
2010-01-27 23:35 ` ron minnich
2010-01-28 9:34 ` Pavel Klinkovsky
3 siblings, 1 reply; 19+ messages in thread
From: Gorka Guardiola @ 2010-01-27 23:30 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
On Wed, Jan 27, 2010 at 6:36 PM, <geoff@plan9.bell-labs.com> wrote:
>
> My long-term goal is to eliminate all the vga drivers but vgavesa,
> which make up about 10% of the pc kernel port by line count. This may
> not be possible due to currently-working graphics cards with broken
> vesa bioses nor desirable because the native drivers are vastly faster
> than the vesa driver (though I think we're closing that gap), but it's
> worth attempting. I've used the vesa driver on my usual plan 9
> terminals and it's hard to see a difference in performance compared
> with the native vga drivers.
>
The problem for me is that many times the vesa modes do not match
the native resolutions on flat screens. This is specially bad in laptops.
I may be wrong but as far as I understand this you
can only use with vesa the modes printed by aux/vga
which are the modes hardwired in the Bios, ¿am I wrong?. I know some
drivers in linux (like in my old vaio) rewrite this modes, would this
be a solution
for this problem?. I don't know nearly enough about vesa...
--
- curiosity sKilled the cat
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 17:36 ` geoff
` (2 preceding siblings ...)
2010-01-27 23:30 ` Gorka Guardiola
@ 2010-01-28 9:34 ` Pavel Klinkovsky
3 siblings, 0 replies; 19+ messages in thread
From: Pavel Klinkovsky @ 2010-01-28 9:34 UTC (permalink / raw)
To: 9fans
> Remember that, on the pc, you should always be able to revert to
> monitor=vesa
Thank you very much for your hint!
In vesa mode my plan9 lives again... ;-)
Pavel
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 13:58 ` [9fans] vgaradeon (was Re: Problem of last update?) Venkatesh Srinivas
2010-01-27 14:10 ` erik quanstrom
2010-01-27 17:36 ` geoff
@ 2010-01-28 4:09 ` arpunk
2010-01-28 4:21 ` arpunk
3 siblings, 0 replies; 19+ messages in thread
From: arpunk @ 2010-01-28 4:09 UTC (permalink / raw)
To: 9fans
> In the short term future, I hope to test the driver on a number of other cards
> and add some PCI IDs/anything-else-needed, such as the R9600, 9800, and 9200/9250.
> Longer-term, my goal is always support for more cards.
I have a RV280 Radeon 9200 card somewhere around.
Will it work right away or do I need to add some PCI IDs to the source?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [9fans] vgaradeon (was Re: Problem of last update?)
2010-01-27 13:58 ` [9fans] vgaradeon (was Re: Problem of last update?) Venkatesh Srinivas
` (2 preceding siblings ...)
2010-01-28 4:09 ` arpunk
@ 2010-01-28 4:21 ` arpunk
3 siblings, 0 replies; 19+ messages in thread
From: arpunk @ 2010-01-28 4:21 UTC (permalink / raw)
To: 9fans
> In the short term future, I hope to test the driver on a number of other cards
> and add some PCI IDs/anything-else-needed, such as the R9600, 9800, and 9200/9250.
> Longer-term, my goal is always support for more cards.
I have a RV280 Radeon 9200 card somewhere around.
Will it work right away or do I need to add some PCI IDs to the source?
^ permalink raw reply [flat|nested] 19+ messages in thread