From: Thomas Mayer <tm.telemotive@gmx.de>
To: barebox@lists.infradead.org
Subject: Re: [PATCH] freescale-mx35-3-stack: support 256 MiB RAM
Date: Fri, 20 Jan 2012 16:04:28 +0100 [thread overview]
Message-ID: <4F19827C.5080601@gmx.de> (raw)
In-Reply-To: <4DB7F14E.1080404@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 891 bytes --]
Hi,
is there a reason why this patch was never applied?
It works fine for us.
Regards,
Thomas
On 27.04.2011 12:34, Marc Kleine-Budde wrote:
> On 04/27/2011 12:32 PM, Roman Fietze wrote:
>> Hello Marc,
>>
>> On Wednesday, 27.April.2011 11:14:54 Marc Kleine-Budde wrote:
>>
>>> Have a look at the /dev folder, do you have two "/dev/mem*"? If not
>>> you should make the .id unique, i.e. should be "0" here.
>> Barebox' register_device auto increments the ID if it's below zero,
>> and devinfo shows me
> Even better!
>
>> ...
>> |----mem2 (ram0)
>> |----mem3 (ram1)
>> ...
>>
>> "My" code is just borrowed from boards/karo-tx25/board.c. So if it's
>> ambiguous, somebody (Sascha? Me?) should fix that there as well.
> Marc
>
>
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
[-- Attachment #1.2: Type: text/html, Size: 1805 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-01-20 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 12:30 Freescale i.MX35 using CSD1 and 256 MiB DDR2 Roman Fietze
2011-04-26 21:56 ` Sascha Hauer
2011-04-27 8:38 ` [PATCH] freescale-mx35-3-stack: support 256 MiB RAM Roman Fietze
2011-04-27 9:14 ` Marc Kleine-Budde
2011-04-27 10:32 ` Roman Fietze
2011-04-27 10:34 ` Marc Kleine-Budde
2012-01-20 15:04 ` Thomas Mayer [this message]
2012-01-23 9:26 ` Sascha Hauer
2012-01-23 14:04 ` Thomas Mayer
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=4F19827C.5080601@gmx.de \
--to=tm.telemotive@gmx.de \
--cc=barebox@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.