Alan Cox wrote:
>
> > The way that I architected the raw NAND flash device driver was to
> > break it into 2 parts. 'nand.c' contains the actual driver code and
> > is considered to be device independent. 'spia.c' is the device
> > dependent part. You should write your own version of 'spia.c'
"Adam J. Richter" wrote:
>
> If there is no architecture on which
> linux-2.4.6-pre8/drivers/mtd/nand/spia.c will compile in its
> "pristine" form, then the CONFIG_MTD_NAND_SPIA should be commented
> out from drivers/mtd/nand/Config.in to avoid wasting the time of
> users and automated
>> linux-2.4.6-pre8/drivers/mtd/nand/spia.c references four
>> undefined symbols, presumably intended to be #define constants,
>> although I am not sure what their values are supposed to be:
>>
>> IO_BASE
>> FIO_BASE
>> PEDR
>> PEDDR
>>
>The way that I
linux-2.4.6-pre8/drivers/mtd/nand/spia.c references four
undefined symbols, presumably intended to be #define constants,
although I am not sure what their values are supposed to be:
IO_BASE
FIO_BASE
PEDR
PEDDR
The way that I architected the raw
Adam J. Richter wrote:
If there is no architecture on which
linux-2.4.6-pre8/drivers/mtd/nand/spia.c will compile in its
pristine form, then the CONFIG_MTD_NAND_SPIA should be commented
out from drivers/mtd/nand/Config.in to avoid wasting the time of
users and automated build
Alan Cox wrote:
The way that I architected the raw NAND flash device driver was to
break it into 2 parts. 'nand.c' contains the actual driver code and
is considered to be device independent. 'spia.c' is the device
dependent part. You should write your own version of 'spia.c' and
So
[EMAIL PROTECTED] said:
> So the Config.in is wrong since I can select spia on x86
Yep. I've added a few more dependencies like that to the map drivers too. I
heard rumours that someone else had done similar changes, but nobody sent me
a patch so those rumours can't be true.
I'll wait for
[EMAIL PROTECTED] said:
> 'spia.c' is the device dependent part. You should write your own
> version of 'spia.c' and "simply" fill in the addresses for the IO
> address and control register address depending on your specific
> hardware. The above symbols are only defined for my specific
> The way that I architected the raw NAND flash device driver was to
> break it into 2 parts. 'nand.c' contains the actual driver code and
> is considered to be device independent. 'spia.c' is the device
> dependent part. You should write your own version of 'spia.c' and
So the Config.in is
"Adam J. Richter" wrote:
>
> linux-2.4.6-pre8/drivers/mtd/nand/spia.c references four
> undefined symbols, presumably intended to be #define constants,
> although I am not sure what their values are supposed to be:
>
> IO_BASE
> FIO_BASE
> PEDR
> PEDDR
>
Adam J. Richter wrote:
linux-2.4.6-pre8/drivers/mtd/nand/spia.c references four
undefined symbols, presumably intended to be #define constants,
although I am not sure what their values are supposed to be:
IO_BASE
FIO_BASE
PEDR
PEDDR
The way
[EMAIL PROTECTED] said:
'spia.c' is the device dependent part. You should write your own
version of 'spia.c' and simply fill in the addresses for the IO
address and control register address depending on your specific
hardware. The above symbols are only defined for my specific hardware.
The way that I architected the raw NAND flash device driver was to
break it into 2 parts. 'nand.c' contains the actual driver code and
is considered to be device independent. 'spia.c' is the device
dependent part. You should write your own version of 'spia.c' and
So the Config.in is wrong
[EMAIL PROTECTED] said:
So the Config.in is wrong since I can select spia on x86
Yep. I've added a few more dependencies like that to the map drivers too. I
heard rumours that someone else had done similar changes, but nobody sent me
a patch so those rumours can't be true.
I'll wait for
14 matches
Mail list logo
