linux-kernel - Re: New true IDE compact flash driver starting point?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4967977E.5010504@softplc.com>
Date:	Fri, 09 Jan 2009 12:29:18 -0600
From:	Dick Hollenbeck <dick@...tplc.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: New true IDE compact flash driver starting point?

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/