On Sun, Jun 29, 2008 at 12:15 AM, Grant Likely
<[EMAIL PROTECTED]> wrote:
> On Thu, Jun 26, 2008 at 09:40:57PM -0600, John Rigby wrote:
>> Because get_immrbase in fsl_soc.c does not work without it.
>
> I think I'd rather see get_immrbase() instead then.
er, I think I'd rather see get_immrbase() *
On Sun, 29 Jun 2008 00:58:12 -0600, Grant Likely wrote:
> On Sun, Jun 29, 2008 at 08:31:43AM +0200, Jean Delvare wrote:
> > Hi Jon, Grant,
> >
> > On Sat, 28 Jun 2008 22:49:40 -0600, Grant Likely wrote:
> > > On Sat, Jun 28, 2008 at 10:05:28PM -0400, Jon Smirl wrote:
> > > > >
> > > > > The driver
On Tue, Jun 24, 2008 at 3:24 PM, John Rigby <[EMAIL PROTECTED]> wrote:
> Move shared code from mpc5121_ads.c to mpc512x_shared.c.
> Add new generic board setup mpc5121_generic.c
>
> Signed-off-by: John Rigby <[EMAIL PROTECTED]>
> ---
> +void __init mpc512x_init_IRQ(void)
> +{
> + struct devic
On Sun, 29 Jun 2008 09:17:25 +0200
"Jean Delvare" <[EMAIL PROTECTED]> wrote:
> Ah, OK. If you use i2c_new_device() then it's alright.
Correct.
I have done the same thing for the i2c-ibm_iic.c driver. Jean, I think
you will like this. It gets rid of the index and the numbered drivers.
And the wal
On Sun, 29 Jun 2008 12:24:39 -0400, Sean MacLennan wrote:
> On Sun, 29 Jun 2008 09:17:25 +0200
> "Jean Delvare" <[EMAIL PROTECTED]> wrote:
>
> > Ah, OK. If you use i2c_new_device() then it's alright.
>
> Correct.
>
> I have done the same thing for the i2c-ibm_iic.c driver. Jean, I think
> you wi
This version adds of_find_i2c_device_by_node() which is needed by ASOC drivers.
To make it work I had to make the i2c bus struct visible. It also picks up a
couple of other minor fixes that have been posted to the lists.
Signed-off-by: Jon Smirl <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/fsl_
Sean MacLennan wrote:
P.S. Do I need a signed-off-by for an RFC?
Signed-off-by: Sean MacLennan <[EMAIL PROTECTED]>
---
Not usually. Some intentionally leave the S-o-b: off of
and RFC specifically to ensure that it stays RFC-ish and
doesn't slip into patchness.
jdl
__
Hi Jon,
> This version adds of_find_i2c_device_by_node() which is needed by ASOC
> drivers.
Cool. I was about to do something similar (of_get_adapter_nr_by_node).
IMHO, the patch should be splitted into the addition of
of_find_i2c_device_by_node()
and the actual patch of i2c-mpc.
Thanks,
Joch
simpleImage should also create an .elf (for xmd or systemAce loading)
If dtbImage and simpleImage could be merged, I'd be all for it...
At some point of course, I need to figure merge the Device Tree in BRAM code
that I've been using, which would be a simpleImage which wouldn't need a device
tr
On Sat, Jun 28, 2008 at 3:49 PM, Grant Likely <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 26, 2008 at 5:29 AM, <[EMAIL PROTECTED]> wrote:
>> From: Michal Simek <[EMAIL PROTECTED]>
>> arch/microblaze/platform/generic/system.dts | 300
>> +++
> Since this is a generated file
On Sunday 29 June 2008, Jean Delvare wrote:
>
> > After the i2c adapter registers itself, of_register_i2c_devices() is called
> > which walks through the child nodes of the i2c adapter node in the device
> > tree. Each child node is an i2c device, and it immediately get
> > registered with the ad
Is there really much of a chance of that, given the differences with the
bootwrappers?
Does anyone care enough about legacy_serial for this to matter? My impression
was that legacy serial was not preferred anyway...
Steve
-Original Message-
From: [EMAIL PROTECTED] on behalf of Grant
On Fri, 2008-06-27 at 08:00 -0500, Kumar Gala wrote:
> On Jun 27, 2008, at 6:27 AM, Paul Mackerras wrote:
>
> > Kumar Gala writes:
> >
> >> Paul, any update on when we might see some of the various patches
> >> pulled into powerpc-next?
> >> I've got some work I'd like to see in .27 but it needs
Yes, Kumar made the same comment. The newer patch that moves the 83xx
add bridge routine to fsl_soc obsoletes this patch.
On Sat, Jun 28, 2008 at 11:38 PM, Grant Likely
<[EMAIL PROTECTED]> wrote:
> On Fri, Jun 20, 2008 at 10:58:38AM -0600, John Rigby wrote:
>> Copied from 83xx minus support for t
Hi Steve,
> In my opionion, we should only include dts files for reference designs, and
> it must be documented how to get the design that the dts corresponds to.
I'm not sure you (or Xilinx) are quite ready for the pain this implies
- have you tried browsing reference designs on Xilinx.com recen
In my opionion, we should only include dts files for reference designs, and it
must be documented how to get the design that the dts corresponds to.
MD5 hashing might be one way to prevent people from getting the dts file wrong,
however without some way of checking it automatically, I don't thin
On Sat, Jun 28, 2008 at 11:36 PM, Grant Likely
<[EMAIL PROTECTED]> wrote:
> Minor comments below.
>
> On Fri, Jun 20, 2008 at 10:58:37AM -0600, John Rigby wrote:
>> Add a interrupt host for the interrupt
>> controller in the mpc5121ads cpld.
>> PCI interrupts are 0-7 the rest are 8-15
>> Touchscree
On Friday 23 May 2008, Grant Likely wrote:
> Question: spi_alloc_device() (and the original code) does a
> spi_master_get() on the spi_master device. Doesn't spi_master_put()
> need to be called when the device is discarded? spi_dev_put() doesn't
> do that explicitly; is it an implicit operation
On Tuesday 17 June 2008, Grant Likely wrote:
> >>> This patch splits the allocation and registration portions of code out
> >>> of spi_new_device() and creates three new functions; spi_alloc_device(),
> >>> spi_register_device(), and spi_device_release().
> >>
> >> I have no problem with the first
On Fri, Jun 27, 2008 at 04:10:17PM -0500, Kumar Gala wrote:
> Added DMA nodes for the elo/elo-plus DMA engines.
>
> Renamed the interrupt controller alias in mpc832x_rdb.dts to ipic so that
> its the same as all the other boards.
>
> Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
[snip]
> diff --
Robert Jennings writes:
> From: Brian King <[EMAIL PROTECTED]>
>
> The Cooperative Memory Overcommit (CMO) on System p does not currently
> support native PCI devices or eBus devices when enabled.
Then why would we get any native PCI or eBus devices in the device
tree?
Paul.
___
Grant Likely writes:
> From: Grant Likely <[EMAIL PROTECTED]>
>
> There have been many questions on and off the mailing list about how
> exactly the bootwrapper is used for embedded targets. Add some
> documentation and help text to try and clarify the system.
>
> Signed-off-by: Grant Likely <[
Modern versions of u-boot create a chosen node automatically. So if
we set the chosen node in the dts file, there will be 2 chosen nodes
passed in to the kernel, and the kernel command line will be taken from
the wrong node. So, remove the extra chosen node from the dts file.
Signed-off-by: C
Hi John, Steve and others,
in generic platform will be generic DTS which I sent in first versions.
This DTS will be for simple platform. There is not copyright.
FDT generator add copyright notice on the top of file. I added it when I start
to program this BSP. Xilinx only add their copyright li
24 matches
Mail list logo