From: Frederik Nosi <fredi@e-salute.it>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG][neofb]2.5.4[0-3]
Date: Thu, 17 Oct 2002 20:01:08 +0000 [thread overview]
Message-ID: <200210172001.08099.fredi@e-salute.it> (raw)
(I'm sending this message to the list becouse mailing you directly bouces)
At first thank you for your reply.
On Thursday 17 October 2002 16:43, you wrote:
> > I have a DELL Latitude CPi D233SP. With kernels from 2.5.40 to 2.5.43
> > using neofb during shutdown I get an Oops:
> >
> > Danger danger! Oopsen imminent
> > MTRR setting reg 2
> >
> > This is the second time I'm reporting this, the first time I CC'ed the
> > mantainer too without results. Here is the link to my previous posting:
> >
> > http://www.cs.helsinki.fi/linux/linux-kernel/2002-39/1108.html
>
> I saw it but I was busy finsihing the fbdev changes that are about to go
> in. I also have this chipset so I plan to track down the bug now that I
> have finished my work.
Ok, no problem, this dont seems as a serious issue so I can live with that.
>
> > With the 2.4.19/20-pre-last kernels scrolling up in the console is very
> > slow using the neofb driver as I've wrote in my previous posting.
>
> What color depth? Acceleration only works for 8 and 16 bpp modes :-(
I'm booting kernels with the " vga=771" option. If I remeber well this is
800x600 with 16bpp. However with this same settings the slowness in scrolling
up dont happens with the latest 2.5 kernels
If you want more info just drop me a mail.
Cheers,
Frederik Nosi
next reply other threads:[~2002-10-17 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 20:01 Frederik Nosi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 14:49 [BUG][neofb]2.5.4[0-3] Frederik Nosi
2002-10-17 16:43 ` [BUG][neofb]2.5.4[0-3] James Simmons
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=200210172001.08099.fredi@e-salute.it \
--to=fredi@e-salute.it \
--cc=linux-kernel@vger.kernel.org \
/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