Skip to contentSkip to conversation

libata: can't set force= on subdevice

DISCUSSION Chris Frey 1 participant 1 message Apr 5, 2013

lore
Share & tools
lore

Chris Frey

author
#0 lore raw

Hi,

Using kernel 3.2.x (Debian Wheezy) and when setting libata.force= kernel command line parameters, there seems to be a conflict with the '.'.

For example, with the following boot argument:

	libata.force=ata1.0:udma/44

I get:

libata: Unknown parameter '0:udma/44'
libata: Unknown parameter '0:udma/44'
libata: Unknown parameter '0:udma/44'
libata: Unknown parameter '0:udma/44'

Which I think is from kernel/params.c, not drivers/ata/libata-core.c.

- Chris