linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: John Rigby <jcrigby@gmail.com>
To: Sylvain Munaut <tnt@246tnt.com>
Cc: Txema Lopez <tlopez@aotek.es>, John Rigby <jrigby@freescale.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Add support for lite5200b board.
Date: Thu, 26 Jan 2006 14:29:18 -0700	[thread overview]
Message-ID: <4b73d43f0601261329n73971003n9217374a1cc2db6f@mail.gmail.com> (raw)
In-Reply-To: <43D807E0.1090206@246tNt.com>

[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]

On 1/25/06, Sylvain Munaut <tnt@246tnt.com> wrote:
>
>
>
> Should apply fine on vanilla. My suggestion for now is take vanilla,
> apply this patch, then the 2-3 patch from Andrey for BestComm and stuff.


I was working on getting bestcomm and fec working, but forward porting
my old 2.6.10 code to current is turning out to be more difficult than I
expected.
If you already have working code then I'll stop working on them.

Where are these patches?  I'm new to this list so I don't have much history.
Would I find these patches in the archive?


I haven't gotten around setup a git tree ... anyone know a good tutorial
> not only on how to checkout stuff but how to well manage a remote
> repository for publishing ?
>
>
> >> Looks good. But two comments :
> >>
> >> * Isn't a modif to the arch/ppc/platform/Makefile missing ?
> >> * What's the "cs-1" you turn on there :
> >>
> >>
> >>
> >>>
> >>> +#ifdef CONFIG_LITE5200B
> >>> +    /* turn on cs1 */
> >>> +    port_config |= 0x80000000;
> >>> +#endif
> >>>
> > What fix this ?
>
> It's to activate the second bank of DDR-SDRAM. However, I find that's
> the job of the bootloader. Fully initializing the memory subsystem is
> one of the few things the kernel expects, so I probably won't include
> this.



I agree completely.

My politics (at least for the 5200 stuff) is the boot loader should :
> * Init memory stuff like it wants (at least boot flash & all dynamic
> mem). The init of some static chipselect could be done in platform init.
> * Put the pin muxes & stuff to the "safest" mode (that is for example
> GPIO Input) execpt for what it requires for boot (like a console PSC and
> ethernet). All other pin mux (defnitive one) should be done in platform
> init depending on the board.
>
>
> >>     I couldn't find the schema / real-doc of the Lite5200b,
> >> is this available somewhere on-line ?
> >>
> > Sylvain, I don't know if there are some Lite5200b doc on line, but I
> > have the schematics and could send to you or to anyone who want it.
>
> Yes, please, I'd appreciate an early copy.
> John sent the link to the User Manual but the latter hasn't the full
> schematic.
>
>
>
> Sylvain
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

[-- Attachment #2: Type: text/html, Size: 3366 bytes --]

  parent reply	other threads:[~2006-01-26 21:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 17:12 [PATCH] Add support for lite5200b board John Rigby
2006-01-24 18:17 ` Sylvain Munaut
2006-01-25 10:24   ` Txema Lopez
2006-01-25 23:21     ` Sylvain Munaut
2006-01-25 23:44       ` Grant Likely
2006-01-26 21:29       ` John Rigby [this message]
2006-01-29 22:21         ` Sylvain Munaut
2006-01-30 18:52           ` John Rigby
2006-01-30 20:29             ` Sylvain Munaut
2006-01-30 21:17               ` John Rigby
2006-01-30 22:17                 ` John Rigby
2006-01-30 22:22                   ` John Rigby
2006-01-30 23:45                     ` Sylvain Munaut

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=4b73d43f0601261329n73971003n9217374a1cc2db6f@mail.gmail.com \
    --to=jcrigby@gmail.com \
    --cc=jrigby@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=tlopez@aotek.es \
    --cc=tnt@246tnt.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).