linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: PRIMA2: make mach-prima2 common for all SiRF series SoC
Date: Tue, 28 Aug 2012 07:28:28 -0700	[thread overview]
Message-ID: <503CD58C.1010703@wwwdotorg.org> (raw)
In-Reply-To: <CAGsJ_4y3Snvf-2DLSrpU5+zmytkARtNxJN_nPdiOngd+BK-aDA@mail.gmail.com>

On 08/28/2012 01:08 AM, Barry Song wrote:
> 2012/8/28 Barry Song <21cnbao@gmail.com>:
>> 2012/8/21 Arnd Bergmann <arnd@arndb.de>:
>>> On Tuesday 21 August 2012, Barry Song wrote:
>>>> then i add these to Kconfig.debug as it is a common way
>>>>
>>>>         config DEBUG_PRIMA2_UART1
>>>>                 bool "Kernel low-level debugging on DaVinci DA8XX using UART1"
>>>>                 depends on ARCH_PRIMA2
>>>>                 help
>>>>                   Say Y here if you want the debug print routines to direct
>>>>                   their output to UART1 serial port on SiRFprimaII devices.
>>>>
>>>>         config DEBUG_MARCO_UART1
>>>>                 bool "Kernel low-level debugging on DaVinci DA8XX using UART2"
>>>>                 depends on ARCH_MARCO
>>>>                 help
>>>>                   Say Y here if you want the debug print routines to direct
>>>>                   their output to UART1 serial port on SiRFmarco devices.
>>>>
>>>> and these in mach-prima2/include/mach/uart.h
>>>>
>>>>   #ifdef CONFIG_DEBUG_PRIMA2_UART1
>>>>   #define SIRFSOC_UART1_PA_BASE          0xb0060000
>>>>   #elif defined(CONFIG_DEBUG_MARCO_UART1)
>>>>   #define SIRFSOC_UART1_PA_BASE          0xcc060000
>>>>   #endif
>>>>
>>>> the above codes seem still ugly ?
>>>>
>>>
>>> No, that's fine, about as a good as it gets with today's kernel
>>> capabilities. Just fix the description to have the correct
>>> SoC name instead of "DaVinci DA8XX" ;-)
>>
>> except the DEBUG_LL uart base address, i missed the zreladdr-y. for
>> primaii, it is 0x00008000, for marco, it is 0x40008000 as marco's
>> memory space begins from 0x4000000.
>> i would to have AUTO_ZRELADDR for the whole SiRF series.
>> but for uImage load address difference in uImage header, which blocks
>> multiple SoCs from using same uImage, is "KERNEL_NOLOAD" uImage type
>> the current generic solution?
> 
> also add Stephen Warren.
> 
> i have two verified ways to resolve this problem:
> 
> 1. use "kernel noload", build uImage by:
> 
> make uImage UIMAGE_TYPE=kernel_noload
> and add the following patch in kernel:

Very recent U-Boot have a bootz command, which acts just like bootm, but
allows use of a raw zImage or the kernel, rather than a
uImage-wrapped-zImage. This was implemented by Marek Vasut.

  reply	other threads:[~2012-08-28 14:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20  8:19 [PATCH 0/3] ARM: PRIMA2: some patches prepared to support new SiRF SoCs Barry Song
2012-08-20  8:19 ` [PATCH 1/3] ARM: PRIMA2: use DT_MACHINE_START and convert to generic board Barry Song
2012-08-20 20:56   ` Arnd Bergmann
2012-08-21  1:49     ` Barry Song
2012-08-21  7:53       ` Arnd Bergmann
2012-08-21  8:26         ` Barry Song
2012-08-21  8:44           ` Arnd Bergmann
2012-08-20  8:19 ` [PATCH 2/3] ARM: PRIMA2: make mach-prima2 common for all SiRF series SoC Barry Song
2012-08-20 21:06   ` Arnd Bergmann
2012-08-21  1:56     ` Barry Song
2012-08-21  7:57       ` Arnd Bergmann
2012-08-21  9:16         ` Barry Song
2012-08-21  9:20           ` Arnd Bergmann
2012-08-28  6:15             ` Barry Song
2012-08-28  8:08               ` Barry Song
2012-08-28 14:28                 ` Stephen Warren [this message]
2012-08-28 14:57                   ` Barry Song
2012-08-21  9:29       ` Barry Song
2012-08-21 10:16         ` Arnd Bergmann
2012-08-21  2:06     ` Barry Song
2012-08-21  7:55       ` Arnd Bergmann
2012-08-20  8:19 ` [PATCH 3/3] ARM: SIRF: make sirf irqchip driver selectable since new SoCs will have GIC Barry Song

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=503CD58C.1010703@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@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 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).