On Wed, Nov 24, 2010 at 10:36:37AM +0100, Radovan Vápeník wrote: > at91_ide_probe chipselect 4 irq 132 res 50000000 > apply_timings t0=600 t1=70 t2=290 t6z=30 > apply_timings mck_hz=99328000 > apply_timings cycle=60 setup=7 pulse=29 data_float=3 > Probing IDE interface ide0... > probing for hda: present=0, media=32, probetype=ATA > probing for hda: present=0, media=32, probetype=ATAPI > probing for hdb: present=0, media=32, probetype=ATA > probing for hdb: present=0, media=32, probetype=ATAPI > ide0 at 0xc4866000-0xc4866007,0xc486e006 on irq 132 We do not detect any IDE device, registers do not contain status/data that IDE layer expect. As far only two possible reasons of that problem come in mind: - board specific code does not reset CF device (with proper reset duration?). This is expected, there is rst_pin in struct at91_cf_data but driver does not use it - CF 9 pin (ATA SEL) is not grounded or set to 0 if connected to controller (also in board specific initialization code) To debug problem further, you can add your own code at the end of at91_ide_probe(), which read/write IDE register to see if device react properly and give some sensible status values. Stanislaw -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
