[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <498CB3CF.8070306@ru.mvista.com>
Date: Sat, 07 Feb 2009 01:03:59 +0300
From: Sergei Shtylyov <sshtylyov@...mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Cc: Atsushi Nemoto <anemo@....ocn.ne.jp>, geert@...ux-m68k.org,
linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
apw@...onical.com
Subject: Re: [PATCH 01/15] ide: include <asm/ide.h> only when needed
Bartlomiej Zolnierkiewicz wrote:
>>Hello.
>>Bartlomiej Zolnierkiewicz wrote:
>>>>>>>+#include <asm/ide.h>
>>>>>>Did you try checkpatch.pl?
>>>>>Sure.
>>>>>This driver uses stuff from <asm-mips/ide.h>.
>>>>>[ I guess I could put '-mips' there to silence warnings on tx493{8,9}.c,
>>>>> however I don't know of the way to get rid of ide-io-std.c's one... ]
>>>>BTW, tx4939ide_{in,out}put_data_swap and
>>>>tx4939ide_{in,out}put_data_swap do exactly same thing.
>>>>If byte-swapped version of ide_{in,out}put_data() were available by
>>>>ide core, they can be used instead. The byte-swapped version of
>>>>default_tp_ops would much helps such queer big-endian platforms. Is
>>>>it worth to bloat ide core? ;-)
>>>Seems to be a good idea and it may also help some other host drivers
>>>(ide-h8300.c?).
>> I'm not sure we need to carry the extra little used code just to help
>>some exotic driver.
> It doesn't seem like we would need to carry any extra extra code for host
> drivers that don't need it because we have flexible Kconfig language to take
> care of such cases, i.e.
> ...
> config CONFIG_IDE_BE_IO
> bool
If it was that simple... Normally the BE case gets handled automagically
(moreover, there is MIPS option that additionally controls I/O and memory
space byte swapping). The case we have to address for TX493x is actually where
the usual magic fails (or actually the code just doesn't want to use that
option). So this doesn't look like a good name to me...
> Thanks,
> Bart
WBR, Sergei
--
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/
Powered by blists - more mailing lists