public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Michael Schmitz <schmitzmic@gmail.com>, <dlemoal@kernel.org>,
	<linux-ide@vger.kernel.org>, <linux-m68k@vger.kernel.org>
Cc: <will@sowerbutts.com>, <rz@linux-m68k.org>,
	<geert@linux-m68k.org>, Finn Thain <fthain@linux-m68k.org>
Subject: Re: [PATCH v4 2/2] ata: pata_falcon: add data_swab option to byte-swap disk data
Date: Wed, 23 Aug 2023 19:35:17 +0300	[thread overview]
Message-ID: <56654dc7-37e7-1fd7-0d3f-647563f4cc5a@omp.ru> (raw)
In-Reply-To: <20230822221359.31024-3-schmitzmic@gmail.com>

On 8/23/23 1:13 AM, Michael Schmitz wrote:

> Some users of pata_falcon on Q40 have IDE disks in default
> IDE little endian byte order, whereas legacy disks use
> host-native big-endian byte order as on the Atari Falcon.
> 
> Add module parameter 'data_swab' to allow connecting drives
> with non-native data byte order. Drives selected by the
> data_swap bit mask will have their user data byte-swapped to
> host byte order, i.e. 'pata_falcon.data_swab=2' will byte-swap
> all user data on drive B, leaving data on drive A in native
> byte order. On Q40, drives on a second IDE interface may be
> added to the bit mask as bits 2 and 3.
> 
> Default setting is no byte swapping, i.e. compatibility with
> the native Falcon or Q40 operating system disk format.
> 
> Cc: William R Sowerbutts <will@sowerbutts.com>
> Cc: Finn Thain <fthain@linux-m68k.org>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Tested-by: William R Sowerbutts <will@sowerbutts.com>
> Signed-off-by: Michael Schmitz <schmitzmic@gmail.com>

Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>

[...]

> diff --git a/drivers/ata/pata_falcon.c b/drivers/ata/pata_falcon.c
> index 3841ea200bcb..7cf15bd9764a 100644
> --- a/drivers/ata/pata_falcon.c
> +++ b/drivers/ata/pata_falcon.c
[...]
> @@ -194,6 +199,9 @@ static int __init pata_falcon_init_one(struct platform_device *pdev)
>  	ata_port_desc(ap, "cmd %px ctl %px data %pa",
>  		      base, ctl_base, &ap->ioaddr.data_addr);
>  
> +	ap->private_data = (void *)(uintptr_t)(pdev->id > 0 ?
> +		pata_falcon_swap_mask >> 2 : pata_falcon_swap_mask);

   How about:

	ap->private_data = (void *)(uintptr_t)(pata_falcon_swap_mask >>
			   (pdev->id > 0 ? 2 : 0));

[...]

MBR, Sergey

  parent reply	other threads:[~2023-08-23 16:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 22:13 [PATCH v4 0/2] Q40 IDE fixes Michael Schmitz
2023-08-22 22:13 ` [PATCH v4 1/2] ata: pata_falcon: fix IO base selection for Q40 Michael Schmitz
2023-08-23  9:05   ` Geert Uytterhoeven
2023-08-24  1:54     ` Michael Schmitz
2023-08-23 16:05   ` Sergey Shtylyov
2023-08-24  1:56     ` Michael Schmitz
2023-08-24 10:00       ` Sergey Shtylyov
2023-08-25  1:07         ` Michael Schmitz
2023-08-22 22:13 ` [PATCH v4 2/2] ata: pata_falcon: add data_swab option to byte-swap disk data Michael Schmitz
2023-08-23  9:10   ` Geert Uytterhoeven
2023-08-23  9:10     ` Geert Uytterhoeven
2023-08-24  1:57       ` Michael Schmitz
2023-08-23 16:35   ` Sergey Shtylyov [this message]
2023-08-23 23:03     ` Damien Le Moal
2023-08-24  1:49       ` 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=56654dc7-37e7-1fd7-0d3f-647563f4cc5a@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=dlemoal@kernel.org \
    --cc=fthain@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rz@linux-m68k.org \
    --cc=schmitzmic@gmail.com \
    --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