linux-stable-rt/arch/cris/arch-v32/drivers
Greg Kroah-Hartman 52840bd628 Kobject: the cris iop_fw_load.c code is broken
This code is really really really broken.  So much so that it's almost
impossible to fix with a simple patch, so just comment out the offending
registration with the kobject core, and mark the driver as broken.

The problem is that the code is trying to register a "raw" struct
device, which is not allowed.  struct device is only for use within the
driver model.  This is being done to try to use the firmware layer which
wants a struct device.  To properly fix this, use something easy, like a
platform device, which is a struct device and can be used for this kind
of thing.

Cc: Mikael Starvik <starvik@axis.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-01-24 20:40:30 -08:00
..
pci
Kconfig ide: move CONFIG_IDE_ETRAX to drivers/ide/Kconfig 2007-11-27 21:35:55 +01:00
Makefile
axisflashmap.c CRIS: remove MTD_AMSTD and MTD_OBSOLETE_CHIPS take two 2007-11-14 18:45:46 -08:00
cryptocop.c
gpio.c
i2c.c
i2c.h
iop_fw_load.c Kobject: the cris iop_fw_load.c code is broken 2008-01-24 20:40:30 -08:00
nandflash.c
pcf8563.c
sync_serial.c