linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dan Williams <dcbw@redhat.com>, Netdev <netdev@vger.kernel.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Jakub Kicinski <kuba@kernel.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: Does anyone use Appletalk?
Date: Thu, 2 Nov 2023 13:13:49 +1100 (AEDT)	[thread overview]
Message-ID: <973278b8-c9e5-b1cf-2e08-2ff8fd8e9aa4@linux-m68k.org> (raw)
In-Reply-To: <d40cd45a-e7e3-49c4-931b-c5ec75a6bf56@app.fastmail.com>

On Wed, 1 Nov 2023, Arnd Bergmann wrote:

> 
> If we had not removed all localtalk support already, ipddp might have 
> been used to bridge between a pre-ethernet mac running macip and an IP 
> based AFP server (netatalk or time machine). Without localtalk support, 
> that is not all that interesting of course.
> 

That line of reasoning misunderstands the value of the localtalk code (and 
conveniently neglects the actual cost of keeping it in-tree).

The existing zilog driver works on all 68k and powerpc Macs with built-in 
serial ports. If we were to complete that driver by adding the missing 
localtalk support, it would create new opportunities for creative 
users/developers who already run Linux on those systems.

Those users/developers would surely derive value from that functionality 
in ways we cannot anticipate, as happens over and over again in the 
(retrocomputing) community.

So the value of the missing zilog localtalk functionality would be 
proportional to the number of Linux systems out there with the necessary 
serial hardware. It's value is not a function of the potential business 
opportunities for your sponsors, despite the prevailing incentives.

It was the potential value of the missing code for localtalk (Zilog SCC) 
and Apple Sound Chip that caused me to place that work near the top of my 
to-do list. But that was several years ago. Unfortunately, with bug fixing 
and recapping, I still can't find time to write the necessary code.

So I can't object to the removal of the localtalk code. But I do object to 
the underhand manner in which it is done.

       reply	other threads:[~2023-11-02  2:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMuHMdWL2TnYmkt2W6=ohBuKmyof8kR3p7ZPzmXmWSGnKj9c3g@mail.gmail.com>
     [not found] ` <594446aaf91b282ff3cbd95953576ffd29f38dab.camel@physik.fu-berlin.de>
     [not found]   ` <CAMuHMdWv=A6MiVwUuOp8zOCcf21HxKb8cdrndzdbAZik3VRXiw@mail.gmail.com>
     [not found]     ` <5e3e52a48ba9cc0109a98cf4c5371c3f80c4b4cc.camel@physik.fu-berlin.de>
     [not found]       ` <79b7f88e3dd6536fe69c63ed3b4cc1f2c551ce8d.camel@redhat.com>
     [not found]         ` <d40cd45a-e7e3-49c4-931b-c5ec75a6bf56@app.fastmail.com>
2023-11-02  2:13           ` Finn Thain [this message]
2023-11-02  8:55             ` Does anyone use Appletalk? 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=973278b8-c9e5-b1cf-2e08-2ff8fd8e9aa4@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=dcbw@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=kuba@kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@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 NNTP newsgroup(s).