On Mon, Feb 28, Antonino A. Daplas wrote:
> On Monday 28 February 2005 04:32, Olaf Hering wrote:
> > On Wed, Feb 23, Linus Torvalds wrote:
> > > This time it's really supposed to be a quickie, so people who can, please
> > > check it out, and we'll make the real 2.6.11 asap.
> >
> > Here is anot
On Mon, Feb 28, Antonino A. Daplas wrote:
> On Monday 28 February 2005 04:32, Olaf Hering wrote:
> > On Wed, Feb 23, Linus Torvalds wrote:
> > > This time it's really supposed to be a quickie, so people who can, please
> > > check it out, and we'll make the real 2.6.11 asap.
> >
> > Here is anot
On Monday 28 February 2005 04:32, Olaf Hering wrote:
> On Wed, Feb 23, Linus Torvalds wrote:
> > This time it's really supposed to be a quickie, so people who can, please
> > check it out, and we'll make the real 2.6.11 asap.
>
> Here is another one, probably not new.
> Is riva_get_EDID_i2c a bit
On Saturday 26 February 2005 09:13, Benjamin Herrenschmidt wrote:
> On Sat, 2005-02-26 at 01:41 +0100, Olaf Hering wrote:
> > modedb can not be __init because fb_find_mode() may get db == NULL.
> > fb_find_mode() is called from modules.
>
> Ahhh, good catch ! I though that was fixed long ago, looks
> This patch has already been posted to linux-fbdev on 2005-02-10 by David
> Vrabel
> and made me ask
> Is there any reason why this has been originally flagged "__init"?
> "vesa_modes" is not "__init". That's why I changed "intelfb" to
> use "vesa_modes".
>
> Maybe time has co
Linus Torvalds wrote:
>
> On Sat, 26 Feb 2005, Olaf Hering wrote:
>
>>modedb can not be __init because fb_find_mode() may get db == NULL.
>>fb_find_mode() is called from modules.
>
>
> Ack. Maybe somebody should run the scripts again to check that we don't
> reference __init data from non-init
On Sat, 2005-02-26 at 00:30 +0100, Olaf Hering wrote:
> On Fri, Feb 25, Olaf Hering wrote:
>
> > On Fri, Feb 25, Olaf Hering wrote:
> >
> > > On Fri, Feb 25, James Simmons wrote:
> > >
> > > >
> > > > > cfb_imageblit(320) dst1 fa51a800 base e0b8 bitstart 1999a800
> > > > > fast_imageblit
On Fri, 2005-02-25 at 22:21 +0100, Olaf Hering wrote:
> On Fri, Feb 25, Olaf Hering wrote:
>
> > On Fri, Feb 25, James Simmons wrote:
> >
> > >
> > > > cfb_imageblit(320) dst1 fa51a800 base e0b8 bitstart 1999a800
> > > > fast_imageblit(237) s daea4000 dst1 fa51a800
> > > > fast_imageblit(2
On Fri, 2005-02-25 at 21:24 +0100, Olaf Hering wrote:
> On Fri, Feb 25, James Simmons wrote:
>
> >
> > > cfb_imageblit(320) dst1 fa51a800 base e0b8 bitstart 1999a800
> > > fast_imageblit(237) s daea4000 dst1 fa51a800
> > > fast_imageblit(269) j 1 fa51a800 0
> > > Unable to handle kernel pagi
On Fri, Feb 25, Olaf Hering wrote:
> On Fri, Feb 25, Olaf Hering wrote:
>
> > On Fri, Feb 25, James Simmons wrote:
> >
> > >
> > > > cfb_imageblit(320) dst1 fa51a800 base e0b8 bitstart 1999a800
> > > > fast_imageblit(237) s daea4000 dst1 fa51a800
> > > > fast_imageblit(269) j 1 fa51a800
On Fri, Feb 25, Olaf Hering wrote:
> On Fri, Feb 25, James Simmons wrote:
>
> >
> > > cfb_imageblit(320) dst1 fa51a800 base e0b8 bitstart 1999a800
> > > fast_imageblit(237) s daea4000 dst1 fa51a800
> > > fast_imageblit(269) j 1 fa51a800 0
> > > Unable to handle kernel paging request at vir
On Fri, Feb 25, James Simmons wrote:
>
> > cfb_imageblit(320) dst1 fa51a800 base e0b8 bitstart 1999a800
> > fast_imageblit(237) s daea4000 dst1 fa51a800
> > fast_imageblit(269) j 1 fa51a800 0
> > Unable to handle kernel paging request at virtual address fa51a800
> >
> > is bitstart incorrec
> cfb_imageblit(320) dst1 fa51a800 base e0b8 bitstart 1999a800
> fast_imageblit(237) s daea4000 dst1 fa51a800
> fast_imageblit(269) j 1 fa51a800 0
> Unable to handle kernel paging request at virtual address fa51a800
>
> is bitstart incorrect or is the thing just not (yet) mapped?
Looks like
13 matches
Mail list logo