public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jens Gehrlein <sew_s@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 3/7 v6] ARM: Add arm1176 core with S3C6400 SoC
Date: Thu, 07 Aug 2008 13:03:30 +0200	[thread overview]
Message-ID: <489AD682.2050104@tqs.de> (raw)
In-Reply-To: <20080807101725.83A2424885@gemini.denx.de>

Wolfgang Denk schrieb:
> In message <489AC866.7070401@tqs.de> you wrote:
>>> That's what we've been doing so far:
>>>
>>> 	-> ls -l include/s3c*
>>> 	-rw-rw-r-- 1 wd wd 21763 Dec  9  2007 include/s3c2400.h
>>> 	-rw-rw-r-- 1 wd wd  7629 Dec  9  2007 include/s3c2410.h
>>> 	-rw-rw-r-- 1 wd wd 38129 Oct 13  2007 include/s3c24x0.h
>> Sorry, don't understand. So is it okay, that these files reside in the 
>> include directory or not?
> 
> Unless you want to submit a clenaup patch for many existing
> processors, yes.
> 
> What is your suggestion instead?

It was just a question to read your opinion. Personally, I can live with 
it. I thought, CPU specific header files had to go to the 
include/asm-<arch>/arch-<cpu> directory.

Sorry for the noise.

Kind regards,
Jens

  reply	other threads:[~2008-08-07 11:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 19:41 [U-Boot-Users] [PATCH 0/7 v6] SMDK6400 support Guennadi Liakhovetski
2008-08-06 19:42 ` [U-Boot-Users] [PATCH 2/7 v6] nand_spl: Support page-aligned read in nand_load, use chipselect Guennadi Liakhovetski
2008-08-06 22:54   ` Scott Wood
2008-08-07  6:36     ` Guennadi Liakhovetski
2008-08-06 19:42 ` [U-Boot-Users] [PATCH 3/7 v6] ARM: Add arm1176 core with S3C6400 SoC Guennadi Liakhovetski
2008-08-07  6:28   ` Andreas Engel
2008-08-07  6:55     ` Guennadi Liakhovetski
2008-08-07  9:33   ` Jens Gehrlein
2008-08-07  9:51     ` Wolfgang Denk
2008-08-07 10:03       ` Jens Gehrlein
2008-08-07 10:17         ` Wolfgang Denk
2008-08-07 11:03           ` Jens Gehrlein [this message]
2008-08-07 11:07             ` Jean-Christophe PLAGNIOL-VILLARD
2008-08-07 10:00   ` Jens Gehrlein
2008-08-07 10:12     ` Guennadi Liakhovetski
2008-08-07 11:12       ` Jens Gehrlein
2008-08-09  9:11   ` Jean-Christophe PLAGNIOL-VILLARD
2008-08-09  9:58     ` [U-Boot] " Wolfgang Denk
2008-08-09 10:07       ` Jean-Christophe PLAGNIOL-VILLARD
2008-08-11  8:17     ` [U-Boot-Users] " Guennadi Liakhovetski
2008-08-06 19:42 ` [U-Boot-Users] [PATCH 4/7 v6] USB: Add support for OHCI controller on S3C6400 Guennadi Liakhovetski
2008-08-07 15:56   ` Markus Klotzbücher
2008-08-07 15:53     ` Jean-Christophe PLAGNIOL-VILLARD
2008-08-08  9:16       ` Markus Klotzbücher
2008-08-06 19:42 ` [U-Boot-Users] [PATCH 5/7 v6] serial: add S3C64XX serial driver Guennadi Liakhovetski
2008-08-09  9:13   ` Jean-Christophe PLAGNIOL-VILLARD
2008-08-11  8:44     ` Guennadi Liakhovetski
2008-08-11 10:06       ` [U-Boot] " Wolfgang Denk
2008-08-11 10:53         ` Guennadi Liakhovetski
2008-08-11 12:12           ` Wolfgang Denk
2008-08-11 12:43             ` Guennadi Liakhovetski
2008-08-06 19:42 ` [U-Boot-Users] [PATCH 6/7 v6] NAND: add NAND driver for S3C64XX Guennadi Liakhovetski
2008-08-07 22:15   ` Scott Wood
2008-08-06 19:42 ` [U-Boot-Users] [PATCH 7/7 v6] ARM: Add support for S3C6400 based SMDK6400 board Guennadi Liakhovetski
2008-08-09  9:32   ` Jean-Christophe PLAGNIOL-VILLARD

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=489AD682.2050104@tqs.de \
    --to=sew_s@tqs.de \
    --cc=u-boot@lists.denx.de \
    /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