linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jordan Crouse" <jordan.crouse@amd.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Martin K. Petersen" <mkp@mkp.net>, Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org
Subject: Re: pata_cs5536: ATA driver for Geode companion chip
Date: Thu, 4 Oct 2007 10:08:34 -0600	[thread overview]
Message-ID: <20071004160834.GA28667@cosmic.amd.com> (raw)
In-Reply-To: <20071004165819.003b86c6@the-village.bc.nu>

On 04/10/07 16:58 +0100, Alan Cox wrote:
> > For kicks I switched my driver over to using PCI config registers
> > instead of MSRs.  And it still worked!
> > 
> > When I changed my driver I did a quickie conversion from wrmsr() to
> > pci_write_config_dword().  If I use pci_write_config_byte() instead
> > (like pata_amd.c), things fail miserably.  A register dump reveals
> > that any value I write becomes a 0.  Yay!
> 
> At that point its probaly a good idea to take CS5536 out of AMD and use
> your driver for it, whether in PCI or MSR mode (or perhaps supporting
> either)

Agreed.  It sounds like there is still breakage in the BIOS - since the
reference VSA code accounts for accesses of different alignments, but its
probably not worth going back and forth about it.  Like I said, if Alan
and Jeff are game, we should go with the 5536 driver, and now that we've
debated it extensively, I'm fine with the MSR accesses - I'm satisfied
that we at least considered the alternative and dismissed it for technically
sound reasons.

Is there anything we can do to make the transition smooth for anybody who
may be using pata_amd in 2.6.23?

Jordan

-- 
Jordan Crouse
Systems Software Development Engineer 
Advanced Micro Devices, Inc.



  reply	other threads:[~2007-10-04 16:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 23:30 pata_cs5536: ATA driver for Geode companion chip Jordan Crouse
2007-10-04  3:29 ` Martin K. Petersen
2007-10-04 12:04   ` Alan Cox
2007-10-04 15:58   ` Alan Cox
2007-10-04 16:08     ` Jordan Crouse [this message]
2007-10-04 16:22       ` Alan Cox
2007-10-04 17:00         ` Martin K. Petersen
2007-10-05  6:05       ` Martin K. Petersen
2007-10-05  6:06       ` [PATCH] pata_cs5536: ATA driver for Geode companion chip (PCI) Martin K. Petersen
2007-10-05  6:07       ` [PATCH] pata_cs5536: ATA driver for Geode companion chip (MSR) Martin K. Petersen
2007-10-05 12:01         ` Alan Cox
2007-10-05 14:53           ` Jordan Crouse
2007-10-05 19:00           ` [PATCH] " Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2007-10-03 17:28 [PATCH 1/1] pata_cs5536: ATA driver for Geode companion chip Martin K. Petersen
2007-10-03 20:31 ` Jordan Crouse
2007-10-03 20:59   ` Alan Cox
2007-10-03 21:18     ` Jordan Crouse
2007-10-03 22:32       ` Martin K. Petersen
2007-10-03 22:56         ` Jeff Garzik
2007-10-10  1:25 ` [PATCH 1/1] " Jeff Garzik
2007-10-10  4:33   ` Martin K. Petersen
2007-10-10 15:20     ` Jordan Crouse
2007-10-10 17:39       ` Andrew Paprocki
2007-10-11  7:22         ` Andrew Paprocki

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=20071004160834.GA28667@cosmic.amd.com \
    --to=jordan.crouse@amd.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=mkp@mkp.net \
    /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).