[RFC] Tosa patches for 2.6.24

[RFC] Tosa patches for 2.6.24

[Dmitry Baryshkov]

Hi,

As some of you know, currently I work on improving the Sharp SL-6000 (tosa)
kernel support. Some parts are going to be merged RSN, some parts are still
in preparation to submission. A pile of patches can't be submitted because
of backwards dependencies. Currently my patchset contains 54 patches.

Now back to support of tosa in OE. I think I have several options:

0) linux-rp-2.6.23 contains support for the device. It has problems, but it's
   mostly working. So leave it just for now, don't touch 2.6.24 and wait for
   2.6.25.
   I would prefer not to follow this path as I want to enlarge testing base
   for patchset and to let tosa-owners use decent kernel features.
1) Add all my patches on the top of linux-rp-2.6.24 as the tosa-specific part.
   This can be hard, as I touch various bits of kernel, this can require
   major efforts.
2) Just start linux-tosa recipe branch, importing few patches from linux-rp,
   and merge them later.
   No major pros et contras.

What would you recommend?

-- 
With best wishes
Dmitry

Re: [RFC] Tosa patches for 2.6.24

[Richard Purdie]

Hi,

On Mon, 2008-01-28 at 00:05 +0000, Dmitry Baryshkov wrote:
> As some of you know, currently I work on improving the Sharp SL-6000 (tosa)
> kernel support. Some parts are going to be merged RSN, some parts are still
> in preparation to submission. A pile of patches can't be submitted because
> of backwards dependencies. Currently my patchset contains 54 patches.
> 
> Now back to support of tosa in OE. I think I have several options:
> 
> 0) linux-rp-2.6.23 contains support for the device. It has problems, but it's
>    mostly working. So leave it just for now, don't touch 2.6.24 and wait for
>    2.6.25.
>    I would prefer not to follow this path as I want to enlarge testing base
>    for patchset and to let tosa-owners use decent kernel features.
> 1) Add all my patches on the top of linux-rp-2.6.24 as the tosa-specific part.
>    This can be hard, as I touch various bits of kernel, this can require
>    major efforts.
> 2) Just start linux-tosa recipe branch, importing few patches from linux-rp,
>    and merge them later.
>    No major pros et contras.

I also prefer 1 or 2. I would like to explain some of the history or
tosa support in linux-rp just so you know why its as it is and how we
could change it.

Currently most of the tosa patches are applied as machine specific. This
was because they contained functionality which broke the other zaurus
machines and the patches were the process of being redesigned so they
didn't do this.

If the patches don't break the other machines, then we're free to apply
them for all machines and they can be applied much earlier in the stack
if they're imminent for upstream.

The advantage of 1 is that the changes get tested on the other zaurus
models and it makes sure there are no adverse affects there. It also has
the advantage you get the benefit of the debugging done on the other
zaurus models, invariably something breaks upstream affecting PXA and
gets fixed in that tree, if you share it, you get that benefit. The
disadvantage as you say is the work can be slightly harder but we can
reorder patches to help with that if appropriate. 

So I have a slight preference for 1 but don't object to 2 if you feel
thats the best way to go.

Regards,

Richard

Re: [RFC] Tosa patches for 2.6.24

[Marcin Juszkiewicz]

Dnia Monday, 28 of January 2008, Richard Purdie napisał:
> Hi,
>
> On Mon, 2008-01-28 at 00:05 +0000, Dmitry Baryshkov wrote:
> > As some of you know, currently I work on improving the Sharp SL-6000
> > (tosa) kernel support. 

Do you want second tosa for testing your work? It sits here unused and is 
property of OpenEmbedded project. I can send it to you on my cost.

> > 1) Add all my patches on the top of linux-rp-2.6.24 as the 
> > tosa-specific part. This can be hard, as I touch various bits of
> > kernel, this can require major efforts.
> > 2) Just start linux-tosa recipe branch, importing few patches from
> > linux-rp, and merge them later.
> >    No major pros et contras.

[..]

> So I have a slight preference for 1 but don't object to 2 if you feel
> thats the best way to go.

Same here.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

             Nonsense. Space is blue and birds fly through it.
             		-- Heisenberg

Re: [RFC] Tosa patches for 2.6.24

[Dmitry Baryshkov]

Marcin Juszkiewicz wrote:

> Dnia Monday, 28 of January 2008, Richard Purdie napisał:
>> Hi,
>>
>> On Mon, 2008-01-28 at 00:05 +0000, Dmitry Baryshkov wrote:
>> > As some of you know, currently I work on improving the Sharp SL-6000
>> > (tosa) kernel support.
> 
> Do you want second tosa for testing your work? It sits here unused and
> is property of OpenEmbedded project. I can send it to you on my cost.

Yes. But there is one problem: Russian customs. Sometimes they can act
like a black hole. Are you going to FOSDEM? If so, I'll try to organize
courier delivery :)

-- 
With best wishes
Dmitry

Re: [RFC] Tosa patches for 2.6.24

[Marcin Juszkiewicz]

Dnia Monday, 28 of January 2008, Dmitry Baryshkov napisał:
> Marcin Juszkiewicz wrote:
> > Dnia Monday, 28 of January 2008, Richard Purdie napisał:
> >> Hi,
> >>
> >> On Mon, 2008-01-28 at 00:05 +0000, Dmitry Baryshkov wrote:
> >> > As some of you know, currently I work on improving the Sharp
> >> > SL-6000 (tosa) kernel support.
> >
> > Do you want second tosa for testing your work? It sits here unused
> > and is property of OpenEmbedded project. I can send it to you on my
> > cost.
>
> Yes. But there is one problem: Russian customs. Sometimes they can act
> like a black hole. Are you going to FOSDEM? If so, I'll try to organize
> courier delivery :)

I am not going for FOSDEM this year - my child will born any day now. But 
Greame will probably be there and he has second OE tosa.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

               We're bad people and we do bad things [Pink]

Re: [RFC] Tosa patches for 2.6.24

[Dmitry Baryshkov]

Marcin Juszkiewicz wrote:

> Dnia Monday, 28 of January 2008, Dmitry Baryshkov napisał:
>> Marcin Juszkiewicz wrote:
>> > Dnia Monday, 28 of January 2008, Richard Purdie napisał:
>> >> Hi,
>> >>
>> >> On Mon, 2008-01-28 at 00:05 +0000, Dmitry Baryshkov wrote:
>> >> > As some of you know, currently I work on improving the Sharp
>> >> > SL-6000 (tosa) kernel support.
>> >
>> > Do you want second tosa for testing your work? It sits here unused
>> > and is property of OpenEmbedded project. I can send it to you on my
>> > cost.
>>
>> Yes. But there is one problem: Russian customs. Sometimes they can act
>> like a black hole. Are you going to FOSDEM? If so, I'll try to organize
>> courier delivery :)
> 
> I am not going for FOSDEM this year - my child will born any day now.
> But Greame will probably be there and he has second OE tosa.



It seems that an attempt to organise a courier failed.
So I would ask you to use a snail-mail to send a device to me.
Probably the best choice would be either DHL or EMS (as Paul suggested).
I can cover shipping costs. I'll send you my address in a private letter.

-- 
With best wishes
Dmitry

Re: [RFC] Tosa patches for 2.6.24

[Paul Sokolovsky]

On Mon, 28 Jan 2008 13:25:31 +0000 (UTC)
Dmitry Baryshkov <dbaryshkov@gmail.com> wrote:

> Marcin Juszkiewicz wrote:
> 
> > Dnia Monday, 28 of January 2008, Richard Purdie napisał:
> >> Hi,
> >>
> >> On Mon, 2008-01-28 at 00:05 +0000, Dmitry Baryshkov wrote:
> >> > As some of you know, currently I work on improving the Sharp
> >> > SL-6000 (tosa) kernel support.
> > 
> > Do you want second tosa for testing your work? It sits here unused
> > and is property of OpenEmbedded project. I can send it to you on my
> > cost.
> 
> Yes. But there is one problem: Russian customs. Sometimes they can act
> like a black hole. 

Did you know about EMS? That's semi-governmental postal service, which
has special provisions for delivery of low-cost personal items w/o
customs duties (and still offers signed delivery and tracking). So,
given a description like "used organizer - gift", and declaration of
$100, you could have very low probability of problems. It works well
for Ukraine, but of course you should check postal law, or at least
talk with EMS agent, for Russia.

> Are you going to FOSDEM? If so, I'll try to
> organize courier delivery :)
>