From: Jens Axboe <axboe@kernel.dk>
To: Lauri Kasanen <cand@gmx.com>, Keith Busch <kbusch@kernel.org>
Cc: linux-mips@vger.kernel.org, tsbogend@alpha.franken.de,
linux-block@vger.kernel.org
Subject: Re: [PATCH 6/6] block: Add n64 cart driver
Date: Mon, 4 Jan 2021 09:28:44 -0700 [thread overview]
Message-ID: <2e65539c-f8f2-d205-527a-0efe2ad8ac95@kernel.dk> (raw)
In-Reply-To: <20210104182720.48a9d74b2b55f5978735eaba@gmx.com>
On 1/4/21 9:27 AM, Lauri Kasanen wrote:
> On Mon, 4 Jan 2021 08:13:32 -0800
> Keith Busch <kbusch@kernel.org> wrote:
>
>>> The media is read-only (but not runtime removable).
>>
>> It's been a while, but I could swear we can save state on these carts.
>> If so, it sounds like that must be separate from the media this driver
>> is accessing, so is that capability provided through a different driver?
>
> Saving uses a separate mechanism, and there are several depending on
> what type of cart it is (no saves, flash, eeprom, or sram). If the cart
> has no save possibility, there is an optional memory card attached to
> the joypad controller.
>
> Currently there is no driver for any of these.
Maybe it'd make sense to make this runtime configurable through configfs
or similar, requiring boot parameters (and hence a reboot to change
them) seems pretty iffy. Similarly, why isn't it available as a module?
--
Jens Axboe
next prev parent reply other threads:[~2021-01-04 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 13:50 [PATCH 6/6] block: Add n64 cart driver Lauri Kasanen
2021-01-04 15:40 ` Jens Axboe
2021-01-04 15:43 ` Lauri Kasanen
2021-01-04 15:49 ` Jens Axboe
2021-01-04 15:56 ` Lauri Kasanen
2021-01-04 16:07 ` Jens Axboe
2021-01-04 15:49 ` Keith Busch
2021-01-04 16:01 ` Lauri Kasanen
2021-01-04 16:13 ` Keith Busch
2021-01-04 16:27 ` Lauri Kasanen
2021-01-04 16:28 ` Jens Axboe [this message]
2021-01-04 16:42 ` Lauri Kasanen
-- strict thread matches above, loose matches on Subject: below --
2020-12-25 17:01 Lauri Kasanen
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=2e65539c-f8f2-d205-527a-0efe2ad8ac95@kernel.dk \
--to=axboe@kernel.dk \
--cc=cand@gmx.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.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