From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v1 2/3] scsi - a2091.c: convert m68k WD33C93 drivers to DMA API
Date: Thu, 30 Jun 2022 08:48:16 +1200 [thread overview]
Message-ID: <39114583-9c4a-7b19-54d5-516feb556fac@gmail.com> (raw)
In-Reply-To: <CAMuHMdX0x3nL5fhmv2T01o8=H6Gp1jog_MZt9gjFe2A7YyMAuQ@mail.gmail.com>
Hi Geert,
On 30/06/22 03:55, Geert Uytterhoeven wrote:
> Hi Michael,
>
> On Wed, Jun 29, 2022 at 9:27 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
>> Most users will opt for loading the kernel to a RAM chunk at a higher
>> physical address, making the lower chunk unusable (except as chip RAM),
>> meaning allocating a bounce buffer within the first 16 MB will most
>> likely fail anyway AIUI (but Geert would know that for sure).
> Exactly. On Zorro III-capable machines, Zorro II RAM is not mapped
> for general use, but can be used by the z2ram block device.
Is there any DMA capable memory other than chip and ZorroII RAM on these
machines?
> Note that you can use it as a bounce buffer, by looking for and marking
> free chunks in the zorro_unused_z2ram bitmap.
That would be similar to what amiga_chip_alloc() does, right? Any
advantages over using chip RAM (faster, perhaps)?
Cheers,
Michael
>
> 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
next prev parent reply other threads:[~2022-06-29 20:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 1:16 [PATCH v1 0/3] Converting m68k WD33C93 drivers to DMA API Michael Schmitz
2022-06-29 1:16 ` [PATCH v1 1/3] scsi - a3000.c: convert " Michael Schmitz
2022-06-29 6:07 ` Arnd Bergmann
2022-06-29 1:16 ` [PATCH v1 2/3] scsi - a2091.c: " Michael Schmitz
2022-06-29 6:06 ` Arnd Bergmann
2022-06-29 7:26 ` Michael Schmitz
2022-06-29 15:55 ` Geert Uytterhoeven
2022-06-29 20:48 ` Michael Schmitz [this message]
2022-06-30 9:27 ` Geert Uytterhoeven
2022-06-30 19:42 ` Michael Schmitz
2022-06-29 1:16 ` [PATCH v1 3/3] scsi - gvp11.c: " Michael Schmitz
2022-06-29 6:02 ` Arnd Bergmann
2022-06-29 6:19 ` [PATCH v1 0/3] Converting " Arnd Bergmann
2022-06-29 7:36 ` Michael Schmitz
2022-06-29 8:20 ` Arnd Bergmann
2022-06-29 15:48 ` Geert Uytterhoeven
2022-06-29 16:44 ` Arnd Bergmann
2022-06-30 2:45 ` Michael Schmitz
2022-06-29 20:28 ` 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=39114583-9c4a-7b19-54d5-516feb556fac@gmail.com \
--to=schmitzmic@gmail.com \
--cc=arnd@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@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