public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Richard Z <rz@linux-m68k.org>, Finn Thain <fthain@linux-m68k.org>
Cc: will@sowerbutts.com, linux-m68k@vger.kernel.org, geert@linux-m68k.org
Subject: Re: [PATCH RFC v3 2/2] m68k/q40: add data_swab option for pata_falcon to byte-swap disk data
Date: Fri, 18 Aug 2023 07:07:39 +1200	[thread overview]
Message-ID: <e332b0d4-0d4e-095d-1fee-1962223798bd@gmail.com> (raw)
In-Reply-To: <F32F62FE-2A74-4648-8BF1-0D1A1E76309B@linux-m68k.org>

Hi Richard,

On 17/08/23 22:27, Richard Z wrote:
> Nitpicking now, there is nothing classic about little endian as all 
> older computers were either big or mid endian.

Right, but IDE was introduced on little endian hardware.

Maybe 'IDE default byte order' would be more exact here.

> It is rather some rare ide host adapters like the Q40 one reversed the 
> byte order of 16bit words which was cheap and convenient in the 
> 1980-9ies but not interoperable with the large majority of other host 
> adapters resulting in a reversed byte/16bit order on disk.

True - installing an IDE disk from e.g. Atari on a Mac, Amiga or PC 
wasn't something you'd have antcipated at that time. Floppy disks were 
for data interchange.

Cheers,

     Michael

>
> Richard

  parent reply	other threads:[~2023-08-17 19:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  3:49 [PATCH RFC v3 0/2] Q40 IDE fixes Michael Schmitz
2023-08-17  3:50 ` [PATCH RFC v3 1/2] m68k/q40: fix IO base selection for Q40 in pata_falcon.c Michael Schmitz
2023-08-17  3:50 ` [PATCH RFC v3 2/2] m68k/q40: add data_swab option for pata_falcon to byte-swap disk data Michael Schmitz
2023-08-17 10:15   ` Finn Thain
2023-08-17 11:47     ` Geert Uytterhoeven
2023-08-17 19:21       ` Michael Schmitz
2023-08-17 21:28         ` Michael Schmitz
2023-08-18 14:33           ` Geert Uytterhoeven
2023-08-18 23:53             ` Finn Thain
2023-08-21  7:46               ` Geert Uytterhoeven
2023-08-21 11:08                 ` Finn Thain
2023-08-21 20:36                   ` Michael Schmitz
2023-08-21 23:18                     ` Finn Thain
     [not found]     ` <F32F62FE-2A74-4648-8BF1-0D1A1E76309B@linux-m68k.org>
2023-08-17 19:07       ` Michael Schmitz [this message]
2023-08-17 19:14     ` Michael Schmitz
2023-08-18  0:36       ` Finn Thain
2023-08-17  3:56 ` [PATCH RFC v3 0/2] Q40 IDE fixes Michael Schmitz
2023-08-17  9:20 ` William R Sowerbutts
2023-08-17 20:25   ` William R Sowerbutts
2023-08-17 21:29     ` 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=e332b0d4-0d4e-095d-1fee-1962223798bd@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=fthain@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rz@linux-m68k.org \
    --cc=will@sowerbutts.com \
    /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