Linux-sh Archive mirror
 help / color / mirror / Atom feed
From: The Mariocrafter <kayvonkamyar@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Unmerged DreamCast Drivers
Date: Sat, 20 Apr 2024 15:01:03 -0700	[thread overview]
Message-ID: <CAEgzAWy-vA=t5tBzaqe4h-esNwtC2pML5NE_uPWnAxvrUmFxxg@mail.gmail.com> (raw)

Hello, the LinuxDC project got abandoned long ago (and got merged with
the main kernel), with a few drivers that were never merged.

The VMUFAT filesystem, to get the DreamCast VMU filesystem working:
https://www.uwsg.indiana.edu/hypermail/linux/kernel/0904.1/02520.html
, a reply with a critique shows at
https://www.uwsg.indiana.edu/hypermail/linux/kernel/0904.1/02545.html
saying that making it not a dependency for the VMU would be
problematic for promoting it's use as a general purpose filesystem,
but being useful for emulator developers. VMUFAT support would be nice
for having Linux on the Dreamcast be able to manage saves, especially
if a homescreen replacement is developed. I think it's better to keep
it Dreamcast-dependant for now, due to security concerns, and due to
having little use outside the Dreamcast, as emulator users can use a
userspace FUSE driver.

Other than that, two full drivers for the VMU's display and the SEGA
LAN Adapter (HIT-0300) have been created, but were not merged nor
pulled, located on the open directory site
https://linuxdc.sourceforge.net/berger/ .

I don't expect the LinuxDC project to return officially, maybe an
unofficial revival, but it's better to get these drivers reviewed and
submitted, and not have it unmerged indefinitely.

             reply	other threads:[~2024-04-20 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-20 22:01 The Mariocrafter [this message]
2024-05-08  9:52 ` Unmerged DreamCast Drivers John Paul Adrian Glaubitz

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='CAEgzAWy-vA=t5tBzaqe4h-esNwtC2pML5NE_uPWnAxvrUmFxxg@mail.gmail.com' \
    --to=kayvonkamyar@gmail.com \
    --cc=linux-sh@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).