linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Fw: [Bugme-new] [Bug 9822] New: mdacon messing up console on hw w/o MDA adapter
Date: Sun, 27 Jan 2008 10:29:48 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801271029010.6515@anakin> (raw)
In-Reply-To: <20080126222433.e1c662d5.akpm@linux-foundation.org>

On Sat, 26 Jan 2008, Andrew Morton wrote:
> Begin forwarded message:
> 
> Date: Sat, 26 Jan 2008 06:00:42 -0800 (PST)
> From: bugme-daemon@bugzilla.kernel.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 9822] New: mdacon messing up console on hw w/o MDA adapter
> 
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=9822
> 
>            Summary: mdacon messing up console on hw w/o MDA adapter
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.24 and before
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: low
>           Priority: P1
>          Component: Console/Framebuffers
>         AssignedTo: jsimmons@infradead.org
>         ReportedBy: devzero@web.de
> 
> 
> Latest working kernel version: didn`t try before 
> Earliest failing kernel version: don`t know, but may exist for a long time
> Distribution: openSuSE
> Hardware Environment: various (e.g. FSC Scenic T 1Ghz i815 PC, FSC Lifebook,
> VMware Workstation)
> Software Environment: -
> 
> Problem Description:
> loading mdacon on a system without MDA adapter screws up the console window. i
> cannot use it afterwards. i would have expected some "no mda adapter found" and
> a clean exit afterwards.
> 
> Steps to reproduce:
> modprobe mdacon
> 
> also see:
> http://marc.info/?l=linux-kernel&m=120082731013963&w=2
> http://uwsg.indiana.edu/hypermail/linux/kernel/0203.3/0524.html
> 
> 
> same issue with cfag12864bfb. behaviour is a little bit different, but console
> is also unusable afterwards.

Cfag12864bfb uses a plain platform device, which doesn't seem to do any
checking for the presence of the appropriate hardware.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      reply	other threads:[~2008-01-27  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27  6:24 Fw: [Bugme-new] [Bug 9822] New: mdacon messing up console on hw w/o MDA adapter Andrew Morton
2008-01-27  9:29 ` Geert Uytterhoeven [this message]

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=Pine.LNX.4.64.0801271029010.6515@anakin \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).