public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: David Miller <davem@davemloft.net>
Cc: lramos.prof@yahoo.com.br, linux-ide@vger.kernel.org, petkovbb@gmail.com
Subject: Re: [PATCH] Fix interface autodetection in legacy IDE driver (trial #2)
Date: Wed, 28 Dec 2016 12:16:18 +0100	[thread overview]
Message-ID: <6105580.S4WFXMp3yn@amdc3058> (raw)
In-Reply-To: <20161227.193818.1314136105272589794.davem@davemloft.net>


Hi,

On Tuesday, December 27, 2016 07:38:18 PM David Miller wrote:
> From: Luiz Carlos Ramos <lramos.prof@yahoo.com.br>
> Date: Tue, 27 Dec 2016 22:33:35 -0200
> 
> > So, ide_generic_init() should test *primary for 1 in the case of an
> > existing IDE primary resource, and *secondary for 1 in the case of a
> > secondary IDE resource.
> > 
> > Unpatched code checks both for zero in order to set the proper bits in
> > probe_mask, and IMHO this is reversed logic.
> 
> Right, and I can't see how this is intentional at all.

If PCI IDE resource is found we shouldn't do the probe automatically
as ide-generic is not the proper driver to run the hardware.  IOW we
only want to do automatic probe if no PCI IDE resources are found (if
primary/secondary == 0).  In such case we are most likely running on
pre-PCI system and should be probing for legacy ISA IDE ports. Please
note they are using the same I/O resources as PCI IDE ones (!).

[ Please see the reply to Luiz for the full explanation. ]

I know that you're busy and don't have time for in-depth analysis
of non-obvious IDE patches.  I would like to help and (co-)maintain 
the IDE subsystem (deep maintenance mode policy would of course be
preserved).

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics


  reply	other threads:[~2016-12-28 11:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12  1:12 [PATCH] Fix interface autodetection in legacy IDE driver (trial #2) Luiz Carlos Ramos
2016-12-26 16:47 ` David Miller
2016-12-27 10:08   ` Bartlomiej Zolnierkiewicz
2016-12-27 16:06     ` Bartlomiej Zolnierkiewicz
2016-12-27 16:41       ` David Miller
2016-12-27 17:25         ` Bartlomiej Zolnierkiewicz
2016-12-28  0:33           ` Luiz Carlos Ramos
2016-12-28  0:38             ` David Miller
2016-12-28 11:16               ` Bartlomiej Zolnierkiewicz [this message]
2016-12-28 11:10             ` Bartlomiej Zolnierkiewicz
2016-12-30  0:52               ` Luiz Carlos Ramos
2016-12-30 16:05                 ` Bartlomiej Zolnierkiewicz
2017-01-09 20:25                   ` David Miller
2017-02-21 14:22                   ` Luiz Carlos Ramos

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=6105580.S4WFXMp3yn@amdc3058 \
    --to=b.zolnierkie@samsung.com \
    --cc=davem@davemloft.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=lramos.prof@yahoo.com.br \
    --cc=petkovbb@gmail.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