Hello,
On Thursday, June 24, 2010 4:08 AM Kyungmin Park wrote:
> On Wed, Jun 23, 2010 at 6:20 PM, Marek Szyprowski
> wrote:
> > Hello,
> >
> > On Wednesday, June 23, 2010 10:02 AM Eric Miao wrote:
> >
> >> >> Now you have
> >> >>
> >> >> s5pv210_device_hsmmc0
> >> >> s5pc100_device_hsmmc0
> >> >
On Wed, Jun 23, 2010 at 6:20 PM, Marek Szyprowski
wrote:
> Hello,
>
> On Wednesday, June 23, 2010 10:02 AM Eric Miao wrote:
>
>> >> Now you have
>> >>
>> >> s5pv210_device_hsmmc0
>> >> s5pc100_device_hsmmc0
>> >> s3c64xx_device_hsmmc0
>> >>
>> >>
>> >> each with a different base.
>> >
>> > Th
On Wednesday, June 23, 2010, Marek Szyprowski wrote:
> Hello,
>
> On Wednesday, June 23, 2010 10:02 AM Eric Miao wrote:
>
>> >> Now you have
>> >>
>> >> s5pv210_device_hsmmc0
>> >> s5pc100_device_hsmmc0
>> >> s3c64xx_device_hsmmc0
>> >>
>> >>
>> >> each with a different base.
>> >
>> > There
Hello,
On Wednesday, June 23, 2010 10:02 AM Eric Miao wrote:
> >> Now you have
> >>
> >> s5pv210_device_hsmmc0
> >> s5pc100_device_hsmmc0
> >> s3c64xx_device_hsmmc0
> >>
> >>
> >> each with a different base.
> >
> > There is no need for such code duplication.
>
> However, I believe this is
On Wed, Jun 23, 2010 at 2:25 PM, Marek Szyprowski
wrote:
> Hello,
>
> On Wednesday, June 23, 2010 3:55 AM Eric Miao wrote:
>
>> ...
>
>> >>> e.g., cpu_is_* usage at OMAP tree
>> >>>
>> >>> static void omap_init_mcspi(void)
>> >>> {
>> >>> if (cpu_is_omap44xx())
>> >>> omap4_m
On Wed, Jun 23, 2010 at 3:28 PM, Tony Lindgren wrote:
> * Eric Miao [100623 03:48]:
>> On Wed, Jun 23, 2010 at 7:27 AM, Kyungmin Park wrote:
>> > To Ben,
>> >
>> > I really need single kernel for s5pc110 (cortex A8) and s5pc210
>> > (cortex A9) at least.
>> > Fortunately arm move to these approa
* Eric Miao [100623 03:48]:
> On Wed, Jun 23, 2010 at 7:27 AM, Kyungmin Park wrote:
> > To Ben,
> >
> > I really need single kernel for s5pc110 (cortex A8) and s5pc210
> > (cortex A9) at least.
> > Fortunately arm move to these approaches recently. but current Samsung
> > SoCs not prepare these o
Hello,
On Wednesday, June 23, 2010 3:55 AM Eric Miao wrote:
> ...
> >>> e.g., cpu_is_* usage at OMAP tree
> >>>
> >>> static void omap_init_mcspi(void)
> >>> {
> >>>if (cpu_is_omap44xx())
> >>>omap4_mcspi_fixup();
> >>>
> >>>platform_device_register(&omap2_mcspi1)
On Wed, Jun 23, 2010 at 10:54 AM, Eric Miao wrote:
> On Wed, Jun 23, 2010 at 9:47 AM, Kyungmin Park wrote:
>> On Wed, Jun 23, 2010 at 9:50 AM, Eric Miao wrote:
>>> On Wed, Jun 23, 2010 at 7:27 AM, Kyungmin Park wrote:
To Ben,
I really need single kernel for s5pc110 (cortex A8) an
On Wed, Jun 23, 2010 at 9:47 AM, Kyungmin Park wrote:
> On Wed, Jun 23, 2010 at 9:50 AM, Eric Miao wrote:
>> On Wed, Jun 23, 2010 at 7:27 AM, Kyungmin Park wrote:
>>> To Ben,
>>>
>>> I really need single kernel for s5pc110 (cortex A8) and s5pc210
>>> (cortex A9) at least.
>>> Fortunately arm mov
On Wed, Jun 23, 2010 at 9:50 AM, Eric Miao wrote:
> On Wed, Jun 23, 2010 at 7:27 AM, Kyungmin Park wrote:
>> To Ben,
>>
>> I really need single kernel for s5pc110 (cortex A8) and s5pc210
>> (cortex A9) at least.
>> Fortunately arm move to these approaches recently. but current Samsung
>> SoCs not
On Wed, Jun 23, 2010 at 7:27 AM, Kyungmin Park wrote:
> To Ben,
>
> I really need single kernel for s5pc110 (cortex A8) and s5pc210
> (cortex A9) at least.
> Fortunately arm move to these approaches recently. but current Samsung
> SoCs not prepare these one.
>
> So I wonder do you have a plan or h
To Ben,
I really need single kernel for s5pc110 (cortex A8) and s5pc210
(cortex A9) at least.
Fortunately arm move to these approaches recently. but current Samsung
SoCs not prepare these one.
So I wonder do you have a plan or how to address these issues?
How to assign the address at resources an
13 matches
Mail list logo
