On Wed, Feb 10, 2010 at 3:20 AM, Wolfgang Grandegger
wrote:
> Wolfgang Grandegger wrote:
>> Hi David,
>>
>> David Miller wrote:
>>> From: Anatolij Gustschin
>>> Date: Tue, 9 Feb 2010 15:23:17 +0100
>>>
In my understanding, in the ESP scsi driver the set of defines for
the register offs
Wolfgang Grandegger wrote:
> Hi David,
>
> David Miller wrote:
>> From: Anatolij Gustschin
>> Date: Tue, 9 Feb 2010 15:23:17 +0100
>>
>>> In my understanding, in the ESP scsi driver the set of defines for
>>> the register offsets is common for all chip drivers. The chip driver
>>> methods for reg
Hi David,
David Miller wrote:
> From: Anatolij Gustschin
> Date: Tue, 9 Feb 2010 15:23:17 +0100
>
>> In my understanding, in the ESP scsi driver the set of defines for
>> the register offsets is common for all chip drivers. The chip driver
>> methods for register access translate the offsets bec
From: Anatolij Gustschin
Date: Tue, 9 Feb 2010 15:23:17 +0100
> In my understanding, in the ESP scsi driver the set of defines for
> the register offsets is common for all chip drivers. The chip driver
> methods for register access translate the offsets because the
> registers on some chips are a
On Thu, 21 Jan 2010 18:03:11 -0800 (PST)
David Miller wrote:
> From: Wolfgang Grandegger
> Date: Thu, 21 Jan 2010 16:25:38 +0100
>
> > Do you see a more clever solution to this problem?
>
> See how we handle this in the ESP scsi driver. We have a set of
> defines for the register offsets, and
Arnd Bergmann wrote:
> On Sunday 24 January 2010, Wolfgang Denk wrote:
>> In message <4b5c5bdf.6020...@grandegger.com> you wrote:
>>> You are probably right and your proposal would likely result in more
>>> transparent (less ugly) code. There has been some discussion about
>>> unifying FEC drivers
On Sunday 24 January 2010, Wolfgang Denk wrote:
> In message <4b5c5bdf.6020...@grandegger.com> you wrote:
> >
> > You are probably right and your proposal would likely result in more
> > transparent (less ugly) code. There has been some discussion about
> > unifying FEC drivers when the patches (w
Dear Wolfgang & Arnd,
In message <4b5c5bdf.6020...@grandegger.com> you wrote:
>
> Arnd Bergmann wrote:
...
> > Is there any chance of building a kernel that runs on both mpc8xx and
> > mpc5121? AFAIK, the 5121 is built on a 6xx core which is fundamentally
> > incompatible with 8xx due to different
Arnd Bergmann wrote:
> On Thursday 21 January 2010, Wolfgang Grandegger wrote:
>> The major problem that Anatolij tries to solve are the different
>> register layouts of the supported SOCs, MPC52xx and MPC8xx. They use the
>> same registers but at different offsets. Therefore we cannot handle
>> th
On Thursday 21 January 2010, Wolfgang Grandegger wrote:
> The major problem that Anatolij tries to solve are the different
> register layouts of the supported SOCs, MPC52xx and MPC8xx. They use the
> same registers but at different offsets. Therefore we cannot handle
> this with a single "fec_t" st
David Miller wrote:
> From: Wolfgang Grandegger
> Date: Thu, 21 Jan 2010 16:25:38 +0100
>
>> Do you see a more clever solution to this problem?
>
> See how we handle this in the ESP scsi driver. We have a set of
> defines for the register offsets, and a set of methods a chip driver
> implements
From: Wolfgang Grandegger
Date: Thu, 21 Jan 2010 16:25:38 +0100
> Do you see a more clever solution to this problem?
See how we handle this in the ESP scsi driver. We have a set of
defines for the register offsets, and a set of methods a chip driver
implements for register accesses.
If the off
Hi Anatolij,
I had a close look...
Anatolij Gustschin wrote:
> drivers/net/fs_enet/*
> Enable fs_enet driver to work 5121 FEC
> Enable it with CONFIG_FS_ENET_MPC5121_FEC
>
> Signed-off-by: John Rigby
> Signed-off-by: Piotr Ziecik
> Signed-off-by: Wolfgang Denk
> Signed-off
David Miller wrote:
> From: Anatolij Gustschin
> Date: Thu, 21 Jan 2010 03:13:18 +0100
>
>> struct fec_info {
>> -fec_t __iomem *fecp;
>> +void __iomem *fecp;
To avoid confusion, the name "base_addr" seems more appropriate as it's
just used to calculate register offsets and for iomap/un
On Thu, 21 Jan 2010 01:22:35 -0800 (PST)
David Miller wrote:
> From: Anatolij Gustschin
> Date: Thu, 21 Jan 2010 03:13:18 +0100
>
> > struct fec_info {
> > - fec_t __iomem *fecp;
> > + void __iomem *fecp;
> ...
> > /* write */
> > -#define FW(_fecp, _reg, _v) __fs_out32(&(_fecp)->fec_ ##
From: Anatolij Gustschin
Date: Thu, 21 Jan 2010 03:13:18 +0100
> struct fec_info {
> - fec_t __iomem *fecp;
> + void __iomem *fecp;
...
> /* write */
> -#define FW(_fecp, _reg, _v) __fs_out32(&(_fecp)->fec_ ## _reg, (_v))
> +#define FW(_regp, _reg, _v) __fs_out32((_regp)->fec_ ## _reg,
drivers/net/fs_enet/*
Enable fs_enet driver to work 5121 FEC
Enable it with CONFIG_FS_ENET_MPC5121_FEC
Signed-off-by: John Rigby
Signed-off-by: Piotr Ziecik
Signed-off-by: Wolfgang Denk
Signed-off-by: Anatolij Gustschin
Cc:
Cc: Grant Likely
---
Changes since previous subm
17 matches
Mail list logo
