From: Michael Schmitz <schmitzmic@googlemail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Thorsten Glaser <tg@mirbsd.de>, linux-m68k@vger.kernel.org
Subject: Re: Debian kernel v2.6.38
Date: Sun, 24 Apr 2011 10:12:54 +1200 [thread overview]
Message-ID: <4DB34EE6.6010004@gmail.com> (raw)
In-Reply-To: <BANLkTimNekxddcHFFV1cAAyiCWsz2EY11g@mail.gmail.com>
Hi Geert,
> On Sat, Apr 23, 2011 at 20:13, Thorsten Glaser <tg@mirbsd.de> wrote:
>
>> • Reserve ST RAM early
>>
>
> Yeah, that's a valid one,
> My (and probably lkml's) main issue there is that it introduces yet
> another custom
> allocator. Can we avoid that?
>
Ideally it would not be an issue if we could properly flag ST-RAM only
as DMA memory. I've tried in the past but setting the max. DMA address
to the 0x00ffffff did have unintended side effects elsewhere in the m68k
mm code.
If there is a generic lowmem allocator, we might be able to use that
instead. It does not need to be available early on, but we need to be
able to reserve some lowmem early.
Another possible hack would be to allocate lowmem early on for each
compiled-in user and store that in a platform device struct for use by
the driver once it initializes. Is there such a thing like early
initcalls for this specific purpose (do a minimum early setup such as
allocate resources, silence IRQs and the like)?.
If all that is not an option (and for the sake of modules needing
ST-RAM), I don't see another way to do it. Some parts of the hardware
just need memory below 0x00ffffff.
Cheers,
Michael
>
>> I’m Bcc’ing the Debian Kernel person I was talking to, so we may
>> get an agreement. I’ll revisit your gitweb later then, to see
>> which patches you actually schedule for Linus, and try to get
>> them into Debian.
>>
>
> As for-2.6.39 got rebased in the mean time, you have to compare
> m68k-v2.6.38 with m68k-queue to see what's (not yet) upstream.
>
> And to back up Christian: keep up the good work!
>
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-04-23 22:13 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 [this message]
2011-04-24 8:18 ` Geert Uytterhoeven
2011-04-24 11:37 ` Thorsten Glaser
2011-04-25 2:36 ` Michael Schmitz
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=4DB34EE6.6010004@gmail.com \
--to=schmitzmic@googlemail.com \
--cc=geert@linux-m68k.org \
--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