linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Ioannis Barkas <jnyb.de@gmail.com>
Cc: linux-ide@vger.kernel.org, dlemoal@kernel.org
Subject: Re: [PATCH v2] ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330
Date: Thu, 22 May 2025 09:39:46 +0200	[thread overview]
Message-ID: <aC7UwqgemO28FGOs@ryzen> (raw)
In-Reply-To: <CADUzMVYk1VOB9u2n4Bxd=ZBeDspkorP94HqA9H1zb6QSDxmFbg@mail.gmail.com>

Hello Ioannis,

Please always CC maintainers.

On Wed, May 21, 2025 at 11:14:47PM +0300, Ioannis Barkas wrote:
> Hello guys!
> 
> cdrecord -vvv -atip produces an error using my AD-7200A on VT6415
> controller at my installation as you can see below:

Do you get this after applying the VT6415 patch in $subject?
Or does this command work on latest kernel without the patch in $subject?

(snip)

> Taso you can update your drive to version 1.09 and retest. Also please
> share a dmesg to identify the errors you get and the kernel in use.
> Output from IDE controller PCI config could be handy:
> sudo lspci -nnnnvvvvxxxxks 05:00.1
> 
> Guys cable detect seems broken. With a 40 conductor cable in Linux I get:
> ata3.00: ATAPI: Optiarc DVD RW AD-7200A, 1.09, max UDMA/66
> also UDMA 4 is selected in hdparm while BIOS says UDMA 2
> 
> Finally cdrecord -vvv -atip command is not working properly with 40
> conductor cable. I get wrong results but no hang was observed at all
> during the tests.

There was a different patch from Tasos WRT 40 wire cable recently:
https://lore.kernel.org/linux-ide/20250519085945.1399466-1-tasos@tasossah.com/

Did you include this patch when testing or not?


Kind regards,
Niklas

  reply	other threads:[~2025-05-22  7:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21 20:14 [PATCH v2] ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 Ioannis Barkas
2025-05-22  7:39 ` Niklas Cassel [this message]
     [not found]   ` <CADUzMVY2_DHqko-863=2f8sU1EtQJXgFeN-_BccnajsYWTpuQA@mail.gmail.com>
2025-05-23  7:31     ` Niklas Cassel
  -- strict thread matches above, loose matches on Subject: below --
2025-05-19  8:49 Tasos Sahanidis
2025-05-20  9:30 ` Damien Le Moal
2025-05-21  8:38   ` Tasos Sahanidis
2025-06-10 12:33 ` Niklas Cassel

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=aC7UwqgemO28FGOs@ryzen \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=jnyb.de@gmail.com \
    --cc=linux-ide@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).