All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dick Hollenbeck <dick@softplc.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New true IDE compact flash driver starting point?
Date: Fri, 09 Jan 2009 12:29:18 -0600	[thread overview]
Message-ID: <4967977E.5010504@softplc.com> (raw)
In-Reply-To: <200901091733.16931.arnd@arndb.de>

Arnd Bergmann wrote:
> On Thursday 08 January 2009, Dick Hollenbeck wrote:
>   
>> I've done something similar to this for 8250 serial ports, but I am 
>> having a difficult time finding out how to do this with pata_platform.c
>>
>>     
>
> Just grep for pata_platform_info to find example code.
>
> 	Arnd <><
>   
Thanks again Arnd.  I did that yesterday and got it working last night!  
The only thing I have questions about are:


1) Since this is for a quasi realtime application, is there any 
advantage to using the interrupt line regarding how the CPU spends its 
idle time waiting for the flash?  (I have an interrupt line I can use.)  
Currently I am not sending in the IRQ resource, resource array length of 
2, not 3.


2) I am getting this message during boot up:  "Driver 'sd' needs 
updating - please use bus_type methods".   Again this is kernel 2.6.26.  
It seems like this can be safely ignored, but if its easy to get rid of 
that I would be happy to back port a patch.



I really appreciate your help.

Dick Hollenbeck


  reply	other threads:[~2009-01-09 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  6:33 New true IDE compact flash driver starting point? Dick Hollenbeck
2009-01-08 12:18 ` Arnd Bergmann
2009-01-08 15:26   ` Dick Hollenbeck
2009-01-09 16:33     ` Arnd Bergmann
2009-01-09 18:29       ` Dick Hollenbeck [this message]
2009-01-09 18:29         ` Alan Cox
2009-01-09 18:35 ` David Daney

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=4967977E.5010504@softplc.com \
    --to=dick@softplc.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.