On Mon, Jan 23, 2006 at 04:12:57PM -0500, Doug Sutherland wrote:
> Due to hardware and support issues, we are not able to upgrade to
> Linux 2.6 at this time.
On Mon, Jan 23, 2006 at 04:55:37PM -0500, Greg KH wrote:
>What are these "hardware and support issues"? Are there drivers present
>in 2
On Tue, Jan 24, 2006 at 03:27:00PM -0500, Doug Sutherland wrote:
> The main issue is the Metrowerks CodeWarrior tools we are using.
> Metrowerks does not yet support Linux 2.6 on the PowerQUICC part and
> they are not committing to support it any time soon.
I'm sure another vendor would be glad to
hope u r using use_acm=1 for windows, and use_acm=0
for linux, while loading the module.
-j
--- Doug Sutherland <[EMAIL PROTECTED]>
wrote:
> We are trying to add a USB device interface to our
> embedded system which
> is running Linux 2.4.26. We have a Linux 2.4
> backport of an early
> vers
On Monday 23 January 2006 1:12 pm, Doug Sutherland wrote:
> We would also like
> to know what issues are involved in backporting this code from 2.6 to
> 2.4.
I think the TTY layer changed enough to make a whole-driver backport
awkward, but the gadget APIs haven't changed appreciably. If you
On Mon, Jan 23, 2006 at 04:12:57PM -0500, Doug Sutherland wrote:
> Due to hardware and support issues, we are not able to upgrade to
> Linux 2.6 at this time.
What are these "hardware and support issues"? Are there drivers present
in 2.4 for your platform that are not present in 2.6? Is there an
We are trying to add a USB device interface to our embedded system which
is running Linux 2.4.26. We have a Linux 2.4 backport of an early
version of the Linux 2.6 Gadget Serial driver (version 1.1.2.1
2004/05/17) running on top of an Arabella Linux USB device driver
running on a Freescale PowerQUI
