The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Gregor Radtke <mail@g-radtke.name>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-kernel@vger.kernel.org, Tim Kunschke <beatmeistah@web.de>
Subject: Re: [PATCH] pata_cs5536 Fix secondary port configuration
Date: Wed, 13 Feb 2008 00:17:01 +0100	[thread overview]
Message-ID: <1202858221.6419.33.camel@desktop.ein-elch.local> (raw)
In-Reply-To: <yq1myq6p7fe.fsf_-_@sermon.lab.mkp.net>

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

Am Dienstag, den 12.02.2008, 09:37 -0500 schrieb Martin K. Petersen:
> Brown paper bag time.  My devel board has a 16MB 1st generation
> compact flash on the secondary so I never noticed this was hosed.
> Please try the following patch...

boots! For some reason, i had to apply it by hand (to 2.6.24.2), and i
was too stupid to examine how to produce a new patch. Looks like i have
to read the documentation at kernelnewbies.org...

Anyway, the patch fits perfectly and now UDMA/33 (due to 40wire-cable,
vendor says UDMA/100 should work either) on a HDD using pata_cs5536 just
works =)

-- 
Jabber: elch@ein-elch.de        PGP: 0x63FC728D
Tel: 0170/238 30 53    http://www.g-radtke.name


[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-02-12 23:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 21:00 pata_cs5536 hangs on boot with hdd attached Gregor Radtke
2008-02-05  6:16 ` Martin K. Petersen
2008-02-10 17:00   ` Gregor Radtke
2008-02-12 14:37     ` [PATCH] pata_cs5536 Fix secondary port configuration Martin K. Petersen
2008-02-12 23:17       ` Gregor Radtke [this message]
2008-02-13  7:12         ` Martin K. Petersen

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=1202858221.6419.33.camel@desktop.ein-elch.local \
    --to=mail@g-radtke.name \
    --cc=beatmeistah@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.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