Hi everyone -
It's good to see that people in the ts-7000 list are actively
maintaining the TS-7xxx port of the latest linux-2.6 kernel.
Matthieu, I've looked at your patchset against 2.6.27.4 - great work!
All of the boards that we use are shipped with 64 MB of ram, so I'm
quite interested to know how the migration goes from DISCONTIGMEM to
SPARSEMEM and ARCH_HAS_FLATMEM_HOLES. I remember when I was doing some
of the earlier work with the 2.6.20 kernel, that there were some
issues with virt_to_phys and vice-versa (from the discontigmem patch)
not really fitting in cleanly.
Today will be my first day of checking out the OpenEmbedded git repo
in order to build a console image for the ts7260 (I believe somebody
mentioned that it is already in upstream). After packaging, I guess
that there will be some platform specific packages, but then the
generic armv4t-linux-gnueabi would be the primary package source. Is
anyone aware of a source for binary packages for the platform-specific
part yet?
I'll see what possible additions I can make. Namely, it would be great
if the userspace fconfig were in there too, so that RedBoot could be
mucked with on a running system. There is a patch for fconfig
specifically for the TS-72xx boards under 'Files' on the yahoo groups
site.
Just out of curiousity, is there a particular git branch for the
'lead' maintainer of the ts-7xxx kernel, or is it mainly done through
OE? Although TS does a decent job providing a reference platform, I
did start up a bit of a $h17$7orm in a recent post saying that we (the
community) should really be using more modern tools as a default, and
rolling a community-driven OE target.
Janne Kario said that he would write up a quick article on Yann
Seiner's Wiki, on how to migrate from the TS distribution to OE. I'm
looking forward to it.
Chris
On Tue, Nov 25, 2008 at 3:23 AM, greywolf9923 <> wrote:
> Hi,
>
> oops, I meant dio_17 indeed. Ok now I understood. About the sparsemem
> problem, I'm discussing with Russell King in the arm mailing list. He
> pointed out that we have to modify even some functions like
> virt_to_phys and phys_to_virt. You can follow the topic here:
>
> http://lists.arm.linux.org.uk/lurker/thread/20081125.081317.43322f89.en.html
>
> --- In Matthieu Crapet <> wrote:
>>
>> Hi,
>>
>> 1) CS# of temperature sensor is connected to DIO_17 according to
>> "TS-7200_Schematic_RevB.pdf" (2004.12.15).
>> DIO_17 is FGPIO_1
>> Remember that FGPIO[3:1] [8mA, PU]. It means that "port F bit 0" does
>> not exist on ep9302.
>> So FGPIO_1 means FGPIO[2].
>>
>> 2) Well, this is a restriction I set. There's no hardware limitiation.
>> (struct spi_board_info ts72xx_spi_bus[] should not be too big).
>>
>> >
>> >
>> > 1) about the spi interface in ts72xx.c: in cs_command you use F gpio 2
>> > as gpio port. I read the ts7200 schematic and I found that the chip
>> > select signal for the temp. chip is dio_16. Dio_16 is connected to the
>> > F gpio port 1 not 2, is there some mistake in the schematic?
>> >
>>
>>
>> > 2) in the spi driver you use 4 as num_chipselect, why? Could you
>> > explain to me?
>> >
>>
>
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|