The problem about 64M, is only when you have for example two banks of
32M with two different chips select. In that case you have that
situation. Instead, if you have only one bank of 64M (512Mbit sdram)
attached for example with the chip select 3, then you have this situation:
0x0000_0000 - 0x007F_FFFF
0x0100_0000 - 0x017F_FFFF
0x0200_0000 - 0x027F_FFFF
0x0300_0000 - 0x037F_FFFF
0x0400_0000 - 0x047F_FFFF
0x0500_0000 - 0x053F_FFFF
0x0600_0000 - 0x067F_FFFF
0x0700_0000 - 0x077F_FFFF
In such case that's no problem.
--- In "charliem_1216" <> wrote:
>
> --- In Matthieu <mcrapet@> wrote:
> >
> > Hi Marco,
> >
> > Thanks for your feedback, I didn't know for ARCH_HAS_FLATMEM_HOLES,
> I will
> > have a look.
>
> First, let me say thanks for trying to keep up support for TS-72xx in
> newer kernels! I read about the plan for moving away from discontimem
> on the LAKML, and wondered how the TS boards would fare.
>
> You probably already know this, but the discontigmem patch is only
> needed if the TS board has 64M or more of RAM. More background is
> here and following threads:
>
http://www.freelists.org/post/linux-cirrus/bootmem-init-node-failure-with-64M-TS7250,6
>
> Quoting from Lennert Buytenhek (ep93xx maintainer):
>
> "The problem here is that Linux 2.6 ep93xx port is somewhat naive and
> expects all RAM to be within a 1G physical address range. This isn't
> always true on ep93xx hardware (such as your board), but it _is_ true
> for all ep93xx hardware I have access to (for example, I have the 32M
> variant of the TS7250), so I never fixed the problem, even though Linux
> supports not having all RAM within a 1G range just fine."
>
> This previous discussion is what helped Breton Saunders generate the
> original discontigmem patch for TS boards, so perhaps it will help
> going forward with SPARSEMEM and ARCH_HAS_FLATMEM_HOLES.
>
> Regards, ........ Charlie
>
> > Concerning LEDS and I2C driver, I will move them to generic GPIO
> driver in
> > the next patch release.
> >
> > Concerning 00-1-ep93xx_gpio_fix.patch
> > It fixes two bugs present in 2.6.27.4.
> > Interrupt enable register offset for port F is wrong (it 0x58 not
0x5C).
> >
> > Regards,
> > Matthieu
> >
>
------------------------------------
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/
|