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: William R Sowerbutts <will@sowerbutts.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Linux 6.4.4 on m68k - Q40 - pata_falcon causes oops at boot time
Date: Tue, 15 Aug 2023 15:30:43 +1200	[thread overview]
Message-ID: <e36baf9d-b027-380c-de91-c9ff52857168@gmail.com> (raw)
In-Reply-To: <AFCD9AA4-7A09-4AF5-B3BE-1C5554BFB8D2@linux-m68k.org>

Hi Richard,

Am 15.08.2023 um 15:05 schrieb Richard Z:
>
>
> On August 14, 2023 11:31:36 PM UTC, Finn Thain <fthain@linux-m68k.org> wrote:
>>
>> On Mon, 14 Aug 2023, Richard Z wrote:
>>
>>>
>>> Well ideally it would be a per-device option. This would help the ide SD
>>> cards greatly and people could byte swap their devices one at a time.
>>>
>>
>> Would a byte-swapping IDE cable help, e.g. if the same flash memory card
>> was moved from an IDE interface to a SCSI interface (on the same Q40)?
>
> The Q40 doesn't have SCSI. The only issue is exchanging devices with other computers.

You could plug one of the old ISA SCSI host adapters into an ISA slot 
(assuming there's more than one).

> Byteswapping cable would help the performance but will also swap the ide ident string so the kernel must take that into account.

That's what pata_falcon does already - 'swap' is true by default to make 
that happen, and gets set to false if data are transfered.

>
>>
>> Perhaps we should not worry too much about unusual use-cases during what
>> would be a temporary transition period...
>
>
> You are right, there are sure many other ways to solve the issue with SD cards.
>
>>> Think of it, if you want to boot an older kernel you don't want to
>>> byteswap your whole hard disk back and forth every time when testing an
>>> older or newer kernel.
>>
>> Probably not an issue for end-users, as they are more likely to boot an
>> old userland together with an old kernel. But potentially an issue for
>> kernel developers who need to mix new kernels with old userland. However,
>> kernel developers can use out-of-tree code to help with their testing, as
>> usual.
>
> Just don't think this transition is worth it if it will make everything more complicated and noticeably slower.

The problem here is that we'd already done the transition to libata / 
pata_falcon and the old IDE code has been removed. Q40 IDE was broken in 
the process.

We need to fix pata_falcon for Q40, and with data on William's disk in 
little endian order, but data on other users' disks in big endian order, 
we need to come up with a way to support both for now.

Cheers,

	Michael

>
> Richard
>

  reply	other threads:[~2023-08-15  3:34 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ZLvZmVfzJNHlPTlJ@sowerbutts.com>
2023-07-23  8:35 ` Linux 6.4.4 on m68k - Q40 - pata_falcon causes oops at boot time Geert Uytterhoeven
2023-07-23  9:59   ` Finn Thain
2023-07-23 15:28     ` William R Sowerbutts
2023-07-24  1:43       ` Finn Thain
2023-07-24 11:09         ` William R Sowerbutts
2023-07-26  7:22           ` Finn Thain
2023-07-23 20:26     ` Michael Schmitz
2023-07-24 11:42       ` William R Sowerbutts
2023-07-24 20:26         ` Michael Schmitz
2023-07-26  9:22           ` Finn Thain
2023-07-26 20:13             ` Michael Schmitz
2023-07-27  1:16               ` Finn Thain
2023-07-27  3:17                 ` Michael Schmitz
2023-07-27 23:47                   ` Finn Thain
2023-07-28  7:21                     ` Geert Uytterhoeven
2023-07-28  7:52                     ` Michael Schmitz
2023-07-28  8:03                       ` Geert Uytterhoeven
2023-07-29  4:56                         ` Michael Schmitz
2023-08-13  3:06                     ` Michael Schmitz
2023-08-13  7:38                       ` Finn Thain
2023-08-13 21:20                         ` Michael Schmitz
2023-08-13 22:24                         ` William R Sowerbutts
2023-08-13 22:54                           ` Michael Schmitz
2023-08-13 23:37                             ` Finn Thain
2023-08-14  0:33                               ` Michael Schmitz
2023-08-14  1:15                                 ` Finn Thain
2023-08-14  2:48                                   ` Michael Schmitz
2023-08-14 11:18                             ` William R Sowerbutts
2023-08-14 20:15                               ` Michael Schmitz
2023-08-14 20:24                                 ` Richard Z
2023-08-14 23:31                                   ` Finn Thain
2023-08-15  3:05                                     ` Richard Z
2023-08-15  3:30                                       ` Michael Schmitz [this message]
2023-08-15  9:49                                         ` William R Sowerbutts
2023-08-15 10:42                                           ` Geert Uytterhoeven
2023-08-15 20:43                                             ` Richard Z
2023-08-15 20:13                                           ` Michael Schmitz
2023-08-15 22:10                                             ` William R Sowerbutts
2023-08-15 22:38                                               ` Michael Schmitz
2023-08-14 20:19                               ` Richard Z
2023-08-14 21:22                                 ` Michael Schmitz
2023-08-15 11:04                                   ` William R Sowerbutts
2023-08-16 17:56                           ` William R Sowerbutts
2023-07-27  7:18               ` Geert Uytterhoeven

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=e36baf9d-b027-380c-de91-c9ff52857168@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=fthain@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.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