On Tue, 9 Aug 2005, Bodo Eggert wrote:
> On Mon, 8 Aug 2005, Benjamin Herrenschmidt wrote:
> > On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
> > > The wrong values are constant across reboots (see my first mail), and I
> > > have a CRT.
> > >
> > > Can you tell me where the timing
On Mon, 8 Aug 2005, Benjamin Herrenschmidt wrote:
> On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
> > The wrong values are constant across reboots (see my first mail), and I
> > have a CRT.
> >
> > Can you tell me where the timing values are read?
>
> radeon_write_mode() programs the
On Mon, 8 Aug 2005, Benjamin Herrenschmidt wrote:
On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
The wrong values are constant across reboots (see my first mail), and I
have a CRT.
Can you tell me where the timing values are read?
radeon_write_mode() programs the mode. The
On Tue, 9 Aug 2005, Bodo Eggert wrote:
On Mon, 8 Aug 2005, Benjamin Herrenschmidt wrote:
On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
The wrong values are constant across reboots (see my first mail), and I
have a CRT.
Can you tell me where the timing values are read?
On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
> The wrong values are constant across reboots (see my first mail), and I
> have a CRT.
>
> Can you tell me where the timing values are read?
radeon_write_mode() programs the mode. The monitor timing infos are read
by the various bits of
On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
The wrong values are constant across reboots (see my first mail), and I
have a CRT.
Can you tell me where the timing values are read?
radeon_write_mode() programs the mode. The monitor timing infos are read
by the various bits of code
On Aug 7, 2005, at 21:13:54, Kyle Moffett wrote:
On Aug 7, 2005, at 12:13:38, Benjamin Herrenschmidt wrote:
_However_ there is an unrelated problem with some panels,
including some
of the 17": The panel doesn't always "sync" properly. This seem to be
related to some subtle timing issue in the
On Aug 7, 2005, at 12:13:38, Benjamin Herrenschmidt wrote:
I've got an LCD, and on mine
it looks like every third pixel-line gets shifted about 32-64
pixels to
the left, and they move with display refresh. My guess is that
something is interrupting radeonfb during a critical time in display
On Sun, 7 Aug 2005, Benjamin Herrenschmidt wrote:
> On Sun, 2005-08-07 at 19:25 +0200, Bodo Eggert wrote:
> > On Sun, 7 Aug 2005, Kyle Moffett wrote:
> > > On Aug 7, 2005, at 03:51:07, Benjamin Herrenschmidt wrote:
> > > > Ah ! Interesting... I don't see why PREEMPT would affect radeonfb
> > > >
On Sun, 2005-08-07 at 19:25 +0200, Bodo Eggert wrote:
> On Sun, 7 Aug 2005, Kyle Moffett wrote:
> > On Aug 7, 2005, at 03:51:07, Benjamin Herrenschmidt wrote:
>
> > > Ah ! Interesting... I don't see why PREEMPT would affect radeonfb
> > > though ... Can you try something like wrapper
On Sun, 7 Aug 2005, Kyle Moffett wrote:
> On Aug 7, 2005, at 03:51:07, Benjamin Herrenschmidt wrote:
> > Ah ! Interesting... I don't see why PREEMPT would affect radeonfb
> > though ... Can you try something like wrapper radeon_write_mode() with
> > preempt_disable()/preempt_enable() and tell me
> I'm having a similar issue with my shiny new 17" Powerbook G4. The
> radeon chip works fine with framebuffer in 2.6.12.4 _with_ PREEMPT,
> but not in 2.6.13-rc5 _with_ PREEMPT (configs are virtually identical).
> I'll try your idea this afternoon when I get the chance.
Note that PREEMPT is
On Aug 7, 2005, at 03:51:07, Benjamin Herrenschmidt wrote:
On Fri, 2005-08-05 at 19:38 +0200, Bodo Eggert wrote:
On Fri, 5 Aug 2005, Benjamin Herrenschmidt wrote:
On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
My CRT is out of sync after radeonfb from 2.6.13-rc5 is
initialized.
On Fri, 2005-08-05 at 19:38 +0200, Bodo Eggert wrote:
> On Fri, 5 Aug 2005, Benjamin Herrenschmidt wrote:
>
> > On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
> > > My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
> > > 2.6.12 does not show this behaviour.
> >
> > I'm
On Fri, 2005-08-05 at 19:38 +0200, Bodo Eggert wrote:
On Fri, 5 Aug 2005, Benjamin Herrenschmidt wrote:
On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
2.6.12 does not show this behaviour.
I'm out of town
On Aug 7, 2005, at 03:51:07, Benjamin Herrenschmidt wrote:
On Fri, 2005-08-05 at 19:38 +0200, Bodo Eggert wrote:
On Fri, 5 Aug 2005, Benjamin Herrenschmidt wrote:
On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
My CRT is out of sync after radeonfb from 2.6.13-rc5 is
initialized.
I'm having a similar issue with my shiny new 17 Powerbook G4. The
radeon chip works fine with framebuffer in 2.6.12.4 _with_ PREEMPT,
but not in 2.6.13-rc5 _with_ PREEMPT (configs are virtually identical).
I'll try your idea this afternoon when I get the chance.
Note that PREEMPT is known
On Sun, 7 Aug 2005, Kyle Moffett wrote:
On Aug 7, 2005, at 03:51:07, Benjamin Herrenschmidt wrote:
Ah ! Interesting... I don't see why PREEMPT would affect radeonfb
though ... Can you try something like wrapper radeon_write_mode() with
preempt_disable()/preempt_enable() and tell me if it
On Sun, 2005-08-07 at 19:25 +0200, Bodo Eggert wrote:
On Sun, 7 Aug 2005, Kyle Moffett wrote:
On Aug 7, 2005, at 03:51:07, Benjamin Herrenschmidt wrote:
Ah ! Interesting... I don't see why PREEMPT would affect radeonfb
though ... Can you try something like wrapper radeon_write_mode()
On Sun, 7 Aug 2005, Benjamin Herrenschmidt wrote:
On Sun, 2005-08-07 at 19:25 +0200, Bodo Eggert wrote:
On Sun, 7 Aug 2005, Kyle Moffett wrote:
On Aug 7, 2005, at 03:51:07, Benjamin Herrenschmidt wrote:
Ah ! Interesting... I don't see why PREEMPT would affect radeonfb
though ... Can
On Aug 7, 2005, at 12:13:38, Benjamin Herrenschmidt wrote:
I've got an LCD, and on mine
it looks like every third pixel-line gets shifted about 32-64
pixels to
the left, and they move with display refresh. My guess is that
something is interrupting radeonfb during a critical time in display
On Aug 7, 2005, at 21:13:54, Kyle Moffett wrote:
On Aug 7, 2005, at 12:13:38, Benjamin Herrenschmidt wrote:
_However_ there is an unrelated problem with some panels,
including some
of the 17: The panel doesn't always sync properly. This seem to be
related to some subtle timing issue in the
On Fri, 5 Aug 2005, Benjamin Herrenschmidt wrote:
> On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
> > My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
> > 2.6.12 does not show this behaviour.
>
> I'm out of town at the moment, could you maybe diff radeonfb between
>
On Fri, 5 Aug 2005, Benjamin Herrenschmidt wrote:
On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
2.6.12 does not show this behaviour.
I'm out of town at the moment, could you maybe diff radeonfb between
working
On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
> My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
> 2.6.12 does not show this behaviour.
I'm out of town at the moment, could you maybe diff radeonfb between
working & non-working and CC me the diff ? I don't have my work
My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
2.6.12 does not show this behaviour.
dmesg from both systems, trimmed down:
2.6.13-rc5:
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Boot video device is :01:00.0
PCI: Using IRQ router VIA [1106/0686] at
My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
2.6.12 does not show this behaviour.
dmesg from both systems, trimmed down:
2.6.13-rc5:
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Boot video device is :01:00.0
PCI: Using IRQ router VIA [1106/0686] at
On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
2.6.12 does not show this behaviour.
I'm out of town at the moment, could you maybe diff radeonfb between
working non-working and CC me the diff ? I don't have my work
28 matches
Mail list logo
