public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@googlemail.com>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: linux-m68k@vger.kernel.org
Subject: Re: Debian kernel v2.6.38
Date: Mon, 25 Apr 2011 14:36:56 +1200	[thread overview]
Message-ID: <4DB4DE48.7040801@gmail.com> (raw)
In-Reply-To: <Pine.BSM.4.64L.1104241134030.8787@herc.mirbsd.org>

Hi Thorsten,
>>  - ataflop, atari_scsi, and atafb allocate ST-RAM only at driver
>> initialization,
>>     
>
> Speaking of atafb, with the trimmed-down patch I get garbled video
> with BootColorDepth 1, 4 or 8, and no option or video=atafb:vga2
> both; using video=atafb:vga4 (with BCD=4) has no output at all.
>   
Patch trimmed down in what respect? No ST-RAM pool allocation at all, or 
atafb trimmed down?
> This is no biggie for me, since the boxen work, but e.g. when
> there’s an “mounted n times” fsck, the machine takes ages longer
> to get up, and people will think it has frozen, so I’d very much
> like to get _some_ kind of fix into at least the second version
> of the Debian kernel, once we get past the initial hurdle…
>   
Geert has given me something to think about with the allocate_resource 
suggestion. If that works at module load time (both ataflop and 
atari_scsi ought to work as modules) it definitely would be the 
preferred way.

Cheers,

  Michael

  reply	other threads:[~2011-04-25  2:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23 18:00 Debian kernel v2.6.38 (was: Re: Fix for SLUB?) Geert Uytterhoeven
2011-04-23 18:13 ` Debian kernel v2.6.38 Thorsten Glaser
2011-04-23 19:19   ` Geert Uytterhoeven
2011-04-23 19:58     ` Thorsten Glaser
2011-04-23 22:12     ` Michael Schmitz
2011-04-24  8:18       ` Geert Uytterhoeven
2011-04-24 11:37         ` Thorsten Glaser
2011-04-25  2:36           ` Michael Schmitz [this message]
2011-04-25 14:19             ` Thorsten Glaser
2011-04-25  1:33     ` Thorsten Glaser
2011-04-24 16:18   ` Finn Thain
2011-04-25  2:48     ` Michael Schmitz
2011-04-25  3:53       ` Finn Thain
2011-04-29 23:44         ` Michael Schmitz
2011-05-08 12:58 ` Debian kernel 2.6.38-5 Thorsten Glaser
2011-05-08 16:59   ` Christian T. Steigies
2011-05-08 18:00     ` Geert Uytterhoeven
2011-05-08 18:49       ` Thorsten Glaser
2011-05-08 19:26         ` Geert Uytterhoeven
2011-05-08 18:40     ` Thorsten Glaser
2011-05-08 20:08       ` Christian T. Steigies
2011-05-08 20:22         ` Geert Uytterhoeven
2011-05-08 20:58         ` Michael Schmitz
2011-05-08 21:45           ` Christian T. Steigies
2011-05-08 21:30         ` Thorsten Glaser
2011-05-08 23:14         ` Finn Thain
2011-05-09  7:16           ` Geert Uytterhoeven
2011-05-09 20:25             ` Christian T. Steigies
2011-05-09 22:49               ` Michael Schmitz
2011-05-10  7:00                 ` Christian T. Steigies
2011-05-10  7:38                   ` Michael Schmitz
2011-05-09 20:28           ` zorro8390 (was: Re: Debian kernel 2.6.38-5) Geert Uytterhoeven
2011-05-10  9:01           ` Debian kernel 2.6.38-5 Geert Uytterhoeven
2011-05-10 11:57             ` Finn Thain
2011-05-10 12:06               ` Geert Uytterhoeven
2011-05-08 20:53   ` Michael Schmitz

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=4DB4DE48.7040801@gmail.com \
    --to=schmitzmic@googlemail.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /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