From: Uros Borovsak <boro@razvoj-verbic.si>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Host USB on MPC8247
Date: Mon, 31 Jul 2006 10:14:21 +0200 [thread overview]
Message-ID: <44CDBBDD.6000401@razvoj-verbic.si> (raw)
In-Reply-To: <44CDBA3C.2040402@compulab.co.il>
Thanks for reply,
I made a mistake while typing the message.
In reality I was asking how difficult would it be to port USB part of
kernel from 2.6.10 to 2.6.13, but I mixed kernel version's when typing.
Mike Rapoport wrote:
> Uros Borovsak wrote:
>
>
>> Hello,
>>
>> Can you at least give me some idea how difficult would it be to patch
>> USB part of kernel from 2.6.13 to 2.6.10?
>>
>>
>>
> As far as I know USB core undergone signifcant changes between 2.6.10
> and 2.6.13. Still it's hard to tell how difficult would it be to
> backport USB from 2.6.13 to 2.6.10.
> Besides, it maybe worth upgrading your kernel instead of backporing
> USB to 2.6.10.
>
>
Upgrading the whole kernel is not a way to go for me here, becouse
company is using montavista kernel, and if I upgrade the whole kernel, I
would have to port all their patches also.
I believe that MontaVista will use higher kernel version some time, so I
wouldn't go backporting driver to 2.6.10, but I would prefer to port USB
part of kernel from 2.6.10 to 2.6.13.
Do you think that is possible and how hard would it be?
Best regards
Uros
>> Are changes only in usb part of kernel, or are there also some
>> changes in other parts of kernel, that I would have to port?
>>
>> Thanks,
>>
>> Best regards
>>
>> Uros
>>
>>
>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>>
>>
>>
>>
>
>
next prev parent reply other threads:[~2006-07-31 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 13:44 Host USB on MPC8247 Uros Borovsak
2006-07-28 11:23 ` Uros Borovsak
2006-07-31 8:07 ` Mike Rapoport
2006-07-31 8:14 ` Uros Borovsak [this message]
2006-07-31 8:23 ` Li Yang-r58472
2006-07-28 12:54 ` Uros Borovsak
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=44CDBBDD.6000401@razvoj-verbic.si \
--to=boro@razvoj-verbic.si \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).