public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] [DRIVERS] <asm/mpc8xxx_spi.h> is only available for ppc boards.
Date: Thu, 24 Jan 2008 12:28:38 -0500	[thread overview]
Message-ID: <4798CAC6.6090308@gmail.com> (raw)
In-Reply-To: <2acbd3e40801240850k6d7a5714n61479666d7cf9afe@mail.gmail.com>

Andy Fleming wrote:
> On Jan 24, 2008 10:33 AM, Peter Pearse <peter.pearse@arm.com> wrote:
>   
>> +#if defined(CONFIG_MPC834X) || \
>> +       defined(CONFIG_MPC8313) || \
>> +       defined(CONFIG_MPC8315) || \
>> +       defined(CONFIG_MPC837X)
>>  #include <asm/mpc8xxx_spi.h>
>> +#endif
>>
>>  #ifdef CONFIG_HARD_SPI
>> ---
>>
>> or should asm-ppc/mpc8xxx_spi.h be moved to drivers/spi?
>>     
>
> Hm.  I'd prefer that, since that SPI driver will possibly propagate
> through *many* variants, and it seems silly to change the driver every
> time we make a new part.  :)
>
> I'm not familiar enough with the device or driver to know whether the
> header is truly ppc-specific, or just coincidentally so.
>
> Andy
>   
The header is specific to this SPI controller, but not really 
PPC-specific. I don't know enough about how Freescale works to know if 
the different divisions such as PPC and Coldfire and whatever else share 
building blocks like these controllers, but conceivably (in my mind at 
least) this could be on anything Freescale makes.

I'm no expert on Kconfig, but I think that once it's in play the 
Makefile for this driver determines whether to even compile the driver 
depending on whether a CONFIG is set or not. I probably forgot to define 
something like CONFIG_MPC8XXX_SPI. Maybe a change to the Makefile is 
needed here?

Sorry for the seemingly random mumblings.

regards,
Ben

  parent reply	other threads:[~2008-01-24 17:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 16:33 [U-Boot-Users] [PATCH] [DRIVERS] <asm/mpc8xxx_spi.h> is only available for ppc boards Peter Pearse
2008-01-24 16:50 ` Andy Fleming
2008-01-24 17:01   ` Kim Phillips
2008-02-08 22:48     ` Ladislav Michl
2008-02-09  0:10       ` Ben Warren
2008-02-09  0:43         ` Ladislav Michl
2008-02-09  2:35           ` Ben Warren
2008-02-11  0:38           ` [U-Boot-Users] u-boot patch submission process Todd Fischer
2008-02-11  4:43             ` Dirk Behme
2008-02-11  8:26               ` Haavard Skinnemoen
2008-02-11 15:03                 ` [U-Boot-Users] Broken (ARM) build, was: " Dirk Behme
2008-02-11 23:25                 ` [U-Boot-Users] " Wolfgang Denk
2008-02-12  9:36                   ` Peter Pearse
2008-02-12 10:22                   ` Haavard Skinnemoen
2008-02-12 22:52                     ` Wolfgang Denk
2008-02-13 19:04                       ` Jerry Van Baren
2008-02-13 22:55                         ` Wolfgang Denk
2008-02-11  9:01               ` Peter Pearse
2008-03-23  0:34           ` [U-Boot-Users] [PATCH] [DRIVERS] <asm/mpc8xxx_spi.h> is only available for ppc boards Wolfgang Denk
2008-03-23  0:46             ` Ben Warren
2008-02-09  0:14       ` Haavard Skinnemoen
2008-01-24 17:28   ` Ben Warren [this message]
2008-01-24 18:18     ` [U-Boot-Users] ppc start.S 'rfmci' opcode not recognized by ppc-440 compiler k b
2008-01-24 23:16       ` Wolfgang Denk

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=4798CAC6.6090308@gmail.com \
    --to=biggerbadderben@gmail.com \
    --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