The high resolution timers and fully preemptive kernel added starting at 2.6.18 will be a very good reason to eventually update, but, I think the time has not come yet, and I would rather see you stick with the 2.4 kernel for now. I think that supporting both
2.6 and 2.4 would just stretch you too thin for right now. We appreciate the support you give through this list, and direct when needed!! Don.
On 1/16/07,
Eddie Dawydiuk <> wrote:
>> If you are recompiling a kernel don't try to compile the SD block
>> driver,
>> use the one we provide.
>
> As it looks now, I'll just stick to using 2.4.26 (based on ts-11) so
> there won't be any problems using the TS compiled version but isn't
> this a problem if you want to (or have to) use a very different
> kernel version? What's the situation when you use a 2.6.x kernel?
The Linux block driver API changed from 2.4 to 2.6 so our driver won't
work with a 2.6 kernel. If, you'd like to develop a device driver(or just
read/write the SD card) for another kernel/OS we provide an OS
independent object file you can link against, it provides routines to
access the SD card. You can find more information here
http://tech.groups.yahoo.com/group/ts-7000/message/3832
> Is there any sort of formal statement from TS on when the 2.6 kernel
> series will be supported?
TS doesn't have a formal statement regarding support of the 2.6 kernel.
Although the topic has been discussed several times on this list, below
is a few responses to this question in the past....
"We are a very old-school set of engineers that have been
well served with the saying "if it ain't broke, don't fix it" and
nothing seems obviously broken with 2.4. This, of course, can change
if 1) we have a large customer legitimately require and/or fund 2.6
development or 2) we can be shown real-life advantages of 2.6 that
outweigh the costs and risks. (Big-Oh notation algorithm
improvements, 200% performance improvements for 1% of apps, driver
updates that can only be described as "better...", or other marketing
dribble are not likely to impress)"
"TS will be more willing to invest resources into 2.6 once there is a
clear winner between Cirrus' 2.6 work and the various others working
independently towards 2.6 on the ep93xx processors. Specifically,
once there is general support for this processor in Linus's official
2.6. Its really too risky for us to get involved at this early stage.
We'd really rather invest energy in making Linux more transparent in
customer applications. What we'd like to do is create a more cohesive
environment with better tools (perhaps Eclipse) and to reduce the need
to understand Linux as much as possible for customer applications. It
is been my experience the people with the best product ideas (and the
resources to see them through) are bright individuals yet know nothing
about Linux and aren't keen to learn. Every time I'm on the phone
with one of these companies/individuals I am embarrased when I have to
explain why they have to use "root=/dev/hda1" in one place and
"/dev/ide0/bus0/target0/part1" in another-- they really shouldn't have
to care. This is the kind of stuff that TS will likely invest in if
we have the spare resources. Right now, we're doing all we can to
keep ahead of our custom and new product designs and software
contracting services."
//Eddie
-- Dr. Don W. Carr J. G. Montenegro 2258 Guadalajara, Mexico +52-333-630-0704 +52-333-836-4500 ext 2930
__._,_.___
![]()
SPONSORED LINKS
__,_._,___
|