From: Luca Santini <luca.santini@spesonline.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] support for edosk7760 board
Date: Fri, 05 Sep 2008 08:14:43 +0000 [thread overview]
Message-ID: <48C0EA73.90402@spesonline.com> (raw)
In-Reply-To: <48B52DC8.1020208@spesonline.com>
Hi Magnus,
sorry for my late...
Yes, i think the patch works in 2.6.27-rcX kernel (addresses are fine
and the chip detected) but i have the irq masking problem that i'm
unable to resolve(my ignorance... i can't imagine what else to use than
make_imask_irq() - i tried your suggestion masking ALSO irqs from 48
to 52 but with no result; i repeat, in .26 masking irq 9 works and in
kernel/irq/manage.c compat_irq_chip_set_default_handler() is called;
otherwise in .27 the function called is __irq_set_trigger(), but with
chip->set_type = NULL), so my .27 kernel won't work in NFS and i can't
say i'm 100% sure it works completely.
(in .26 it don't work because of the lack of 'lp' structure... )
p.s.: a little question git-related... (i'm moving my first steps with
git..) :
if i pull from
master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git
it asks for a password.... ???
currently, i pull from
git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6.git
is it the same?
Magnus Damm wrote:
> Hi Luca,
>
> On Thu, Aug 28, 2008 at 8:50 PM, Magnus Damm <magnus.damm@gmail.com> wrote:
>> On Thu, Aug 28, 2008 at 12:00 PM, Paul Mundt <lethal@linux-sh.org> wrote:
>>> On Wed, Aug 27, 2008 at 06:32:02PM +0200, Luca Santini wrote:
>>>>>>> +static struct smc91x_platdata smc91x_info = {
>>>>>>> + .flags = SMC91X_USE_16BIT,
>>>>>>> +};
>>>>>>> +
>>>>> For some reason your flags here and your later smc91x patch for edosk7760
>>>>> have absolutely nothing in common. This leads me to believe that you
>>>>> either couldn't get the dynamic configuration working, in which case this
>>>>> bit of code is useless, or that it works fine and there's no need for the
>>>>> changes to smc91x.h. If you need both, you are doing something very
>>>>> wrong.
>>>>>
>>>> you're right; what i really need is
>>>>
>>>> #define SMC_IO_SHIFT 1
>>>>
>>>> but using the platdata flag
>>>>
>>>> SMC91X_IO_SHIFT_1
>>>>
>>>> doesn't work.
>>>>
>>> Ok, so that's a real bug then. Magnus, can you take a look at this?
>> The io shift platform data configuration should be generic, but it
>> looks like it has been fully hooked in by some ARM platforms only at
>> this point. Someone forgot to fix the generic case. Try the attached
>> patch, that should get you going. Let me know if it solves your issue.
>
> Did the patch help?
>
> Thanks,
>
> / magnus
>
>
next prev parent reply other threads:[~2008-09-05 8:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 10:34 [PATCH] support for edosk7760 board Luca Santini
2008-08-27 11:12 ` Manuel Lauss
2008-08-27 14:55 ` Paul Mundt
2008-08-28 3:00 ` Paul Mundt
2008-08-28 11:50 ` Magnus Damm
2008-08-29 8:35 ` Luca Santini
2008-09-01 1:24 ` Magnus Damm
2008-09-01 8:11 ` Luca Santini
2008-09-05 8:14 ` Magnus Damm
2008-09-05 8:14 ` Luca Santini [this message]
2008-09-05 8:17 ` Magnus Damm
2008-09-05 8:30 ` Magnus Damm
2008-09-05 8:33 ` Manuel Lauss
2008-09-05 8:46 ` Magnus Damm
2008-09-05 8:48 ` Paul Mundt
2008-09-05 9:01 ` Manuel Lauss
2008-09-05 10:16 ` Luca Santini
2008-09-05 14:14 ` Luca Santini
2008-09-08 2:26 ` Magnus Damm
2008-09-08 2:30 ` Paul Mundt
2008-09-08 2:52 ` Paul Mundt
2008-09-08 5:41 ` Manuel Lauss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48C0EA73.90402@spesonline.com \
--to=luca.santini@spesonline.com \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox