On Thursday 03 January 2008, Li Li wrote:
* The detection method for the primary bus is somewhat fragile,
because
we depend on the order of the nodes in the device tree, which is not
specified to have a meaning. /Maybe/ there could be a property in
(at most) one of the PCI host bridge
On Thu, 2008-01-03 at 16:14 +0800, Arnd Bergmann wrote:
On Thursday 03 January 2008, Li Li wrote:
* The detection method for the primary bus is somewhat fragile,
because
we depend on the order of the nodes in the device tree, which is
not
specified to have a meaning. /Maybe/
On Wed, Jan 02, 2008 at 12:12:00PM -0500, Jon Smirl wrote:
On 1/2/08, Grant Likely [EMAIL PROTECTED] wrote:
On 1/2/08, Jon Smirl [EMAIL PROTECTED] wrote:
On 1/2/08, Timur Tabi [EMAIL PROTECTED] wrote:
mpc8610_hpcd is the harder one to load since it doesn't have a device
tree entry.
On Wed, Jan 02, 2008 at 12:21:02PM -0600, Jon Loeliger wrote:
Folks,
I'd like to release a DTC 1.1 Real Soon Now!
However, I've been back-logged due to the holidays.
If you have any outstanding DTC or libfdt patches
that I have not yet applied and that you would like
in that release,
On Wed, Jan 02, 2008 at 09:29:57AM -0600, Timur Tabi wrote:
Jon Smirl wrote:
On 12/19/07, Timur Tabi [EMAIL PROTECTED] wrote:
sound/soc/fsl/fsl_ssi.c | 614 +++
sound/soc/fsl/fsl_ssi.h | 224 +++
I'm confused about this
On Thu, 3 Jan 2008 01:32:21 -0600 Milton Miller [EMAIL PROTECTED] wrote:
Hmmm, in-reply-to on the web archive is broken again, sfr alerted.
Just a test ...
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
http://www.canb.auug.org.au/~sfr/
On Thursday 03 January 2008, Li Li wrote:
It's easy enough to just panic() if you find more than one primary
bus,
since the information from the device tree is static enough that one
will know how to fix this after seeing the error.
It is just a case. what about if do not find
On Thu, 2008-01-03 at 18:14 +0800, Arnd Bergmann wrote:
After some more research, I noticed that the distinction between
primary and secondary host bridges will go away _anyway_, so
I guess we shouldn't worry about it too much.
On powerpc64, we already don't care, as the
Hi David,
+/ {
+model = unknown,dbox2; // boot wrapper fills in correct manufacturer
Probably better just to leave model out of the dts and let the
bootwrapper add it.
Unfortunately, dtc requires a model:
$ dtc arch/powerpc/boot/dts/dbox2.dts
DTC: dts-dts on file
So, like, the other day David Gibson mumbled:
I posted this one a while back, but I guess it dropped through the
cracks.
Yep, sorry.
There's also the patch I sent you quite a long time ago that
adds a clarifying readme about the licensing situation - that might be
an idea for v1.1, too.
On 1/2/08, David Gibson [EMAIL PROTECTED] wrote:
On Wed, Jan 02, 2008 at 12:12:00PM -0500, Jon Smirl wrote:
On 1/2/08, Grant Likely [EMAIL PROTECTED] wrote:
On 1/2/08, Jon Smirl [EMAIL PROTECTED] wrote:
On 1/2/08, Timur Tabi [EMAIL PROTECTED] wrote:
mpc8610_hpcd is the harder one to
On Sep 25, 2007 1:18 PM, Mike Nuss [EMAIL PROTECTED] wrote:
Is there a reason that booke_wdt.c does not specify a MODULE_LICENSE?
From the copyright notice at the top it appears to be GPL. As
written,
it taints the kernel.
Odd, no reason. I'll submit a patch for that.
Also,
So, like, the other day Paul Gortmaker mumbled:
Here is a small patch to clean up the usage info and the error returns
for ftdump -- not sure what the future holds for ftdump vs. simply using
dtc -I dtb -O dts someblob.dtb ...
Paul.
Paul,
Any chance of a signed-off-by line?
Thanks,
jdl
On 1/2/08, David Gibson [EMAIL PROTECTED] wrote:
On Wed, Jan 02, 2008 at 09:29:57AM -0600, Timur Tabi wrote:
Jon Smirl wrote:
On 12/19/07, Timur Tabi [EMAIL PROTECTED] wrote:
sound/soc/fsl/fsl_ssi.c | 614 +++
sound/soc/fsl/fsl_ssi.h
Here is a small patch to clean up the usage info and the error returns
for ftdump -- not sure what the future holds for ftdump vs. simply using
dtc -I dtb -O dts someblob.dtb ...
Paul.
diff --git a/ftdump.c b/ftdump.c
index 53343d7..49bc7cf 100644
--- a/ftdump.c
+++ b/ftdump.c
@@ -8,6 +8,8 @@
Jon Loeliger wrote:
So, like, the other day Paul Gortmaker mumbled:
Here is a small patch to clean up the usage info and the error returns
for ftdump -- not sure what the future holds for ftdump vs. simply using
dtc -I dtb -O dts someblob.dtb ...
Paul.
Paul,
Any chance of a
From: Mark A. Greer [EMAIL PROTECTED]
Fix error in booting-without-of.txt that indicates that a node can inherit
its #address-cells and #size-cells definitions from its parent's parent.
This is not correct.
Signed-off-by: Mark A. Greer [EMAIL PROTECTED]
---
On Wed, Jan 02, 2008 at 07:46:40PM -0600, Josh Boyer wrote:
On Wed, 2 Jan 2008 17:07:50 -0700
Mark A. Greer [EMAIL PROTECTED] wrote:
From: Mark A. Greer [EMAIL PROTECTED]
Fix error in booting-without-of.txt that indicates that a node can inherit
its #address-cells and #size-cells
On Thu, 3 Jan 2008 08:32:56 -0700
Mark A. Greer [EMAIL PROTECTED] wrote:
On Wed, Jan 02, 2008 at 07:46:40PM -0600, Josh Boyer wrote:
On Wed, 2 Jan 2008 17:07:50 -0700
Mark A. Greer [EMAIL PROTECTED] wrote:
From: Mark A. Greer [EMAIL PROTECTED]
Fix error in booting-without-of.txt
On Wed, Jan 02, 2008 at 12:32:51PM -0700, Grant Likely wrote:
From: Grant Likely [EMAIL PROTECTED]
Signed-off-by: Grant Likely [EMAIL PROTECTED]
---
arch/powerpc/platforms/8xx/ep88xc.c |5 ++---
arch/powerpc/platforms/8xx/mpc885ads_setup.c |5 ++---
How about
On 1/3/08, Scott Wood [EMAIL PROTECTED] wrote:
On Wed, Jan 02, 2008 at 12:32:51PM -0700, Grant Likely wrote:
From: Grant Likely [EMAIL PROTECTED]
Signed-off-by: Grant Likely [EMAIL PROTECTED]
---
arch/powerpc/platforms/8xx/ep88xc.c |5 ++---
Jon Smirl wrote:
On 1/2/08, Timur Tabi [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
On 1/1/08, Jon Smirl [EMAIL PROTECTED] wrote:
On 12/19/07, Timur Tabi [EMAIL PROTECTED] wrote:
+ [EMAIL PROTECTED] {
+ compatible = fsl,ssi;
+
Jon Smirl wrote:
For this model to work you need to split your driver. fsl-ssi and
mpc8610_hpcd need to be in two separate drivers.
They are two separate drivers. sound/soc/fsl/fsl_ssi.c and
sound/soc/fsl/mpc8610_hpcd.c
fsl-ssi is easy
enough to load since it has a device tree entry.
Grant Likely wrote:
Why not be a child of the i2c bus with a phandle to the ssi bus?
Because when I probe the SSI node, I want to know what the attached codec is.
So if anything, I would need a pointer from the SSI bus *to* the respective
child on the I2C bus.
I know little about platform
Grant Likely wrote:
Does that mean with ASoC V2 you can instantiate it with the board
specific platform code instead?
I don't know. I haven't really looked at V2 yet. You'll have to ask Liam
Girdwood.
This is one of the examples of where the compatible properties are
trying to be far to
On 1/3/08, Timur Tabi [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
Don't we want to follow the device tree policy of putting the device
on the controlling bus and then link it to the data bus?
Normally, that sounds like a good idea, but the cs4270 is an I2S device first,
and an I2C device
Mark Brown wrote:
The machine support code (fabric driver in PowerPC terms, I think?)
tells the core how everything is connected together by registering
devices representing the links (eg, I2S) between the codecs, CPU and
other devices. The ASoC core is then responsible for ensuring that all
David Gibson wrote:
Instantiating the fabric driver off any node is wrong, precisely
because it is an abstraction. The fabric driver should be
instantiated by the platform code.
Can you tell me how to do that?
--
Timur Tabi
Linux Kernel Developer @ Freescale
On 1/3/08, Timur Tabi [EMAIL PROTECTED] wrote:
Grant Likely wrote:
Why not be a child of the i2c bus with a phandle to the ssi bus?
Because when I probe the SSI node, I want to know what the attached codec is.
So if anything, I would need a pointer from the SSI bus *to* the respective
Grant Likely wrote:
The device tree is a description of the hardware; not software. It's
not a good idea to break with convention due to current driver
architecture.
I believe that with ASoC V1, I'm stuck between a rock and a hard place, and so
the only way to make this code work is to bend
Mark Brown wrote:
clock1 = 0, bb8000
Would that be better?
To cover everything you'd need to be able to specify all the clocking
parameters, especially a PLL configuration, and also specify more than
one of each item. Even then you'd still have problems like...
The ASoC V1 API for
Scott Wood wrote:
+static struct of_platform_driver ucc_uart_of_driver = {
+ .owner = THIS_MODULE,
+ .name = ucc_uart,
Maybe better fsl,ucc_uart?
fsl,qe-uart is defined by Documentation/powerpc/booting-without-of.txt.
Wait, I'm confused. What does the
On 1/3/08, Timur Tabi [EMAIL PROTECTED] wrote:
Grant Likely wrote:
Does that mean with ASoC V2 you can instantiate it with the board
specific platform code instead?
I don't know. I haven't really looked at V2 yet. You'll have to ask Liam
Girdwood.
This is one of the examples of where
Timur Tabi wrote:
Scott Wood wrote:
+static struct of_platform_driver ucc_uart_of_driver = {
+.owner = THIS_MODULE,
+.name = ucc_uart,
Maybe better fsl,ucc_uart?
fsl,qe-uart is defined by Documentation/powerpc/booting-without-of.txt.
Wait, I'm confused. What does
On 1/3/08, Timur Tabi [EMAIL PROTECTED] wrote:
Grant Likely wrote:
The device tree is a description of the hardware; not software. It's
not a good idea to break with convention due to current driver
architecture.
I believe that with ASoC V1, I'm stuck between a rock and a hard place,
On 1/3/08, Timur Tabi [EMAIL PROTECTED] wrote:
Grant Likely wrote:
Make the compatible property tell you! :-) If it's connected to an
I2S codec, then it could be compatible = fsl,mpc8610-ssi,i2s. Or
for AC7, compatible = fsl,mpc8610-ssi,ac97
That won't work. There are too many
Grant Likely wrote:
On 1/3/08, Timur Tabi [EMAIL PROTECTED] wrote:
Grant Likely wrote:
Why not be a child of the i2c bus with a phandle to the ssi bus?
Because when I probe the SSI node, I want to know what the attached codec is.
So if anything, I would need a pointer from the SSI bus *to*
Grant Likely wrote:
Make the compatible property tell you! :-) If it's connected to an
I2S codec, then it could be compatible = fsl,mpc8610-ssi,i2s. Or
for AC7, compatible = fsl,mpc8610-ssi,ac97
That won't work. There are too many variations. I think a separate property
just makes more
Grant Likely wrote:
On 1/3/08, Scott Wood [EMAIL PROTECTED] wrote:
I'd just link in both directions, and let software follow it in
whichever direction it prefers.
Gah! Don't do that! Then you need to maintain both directions in the
dts file. Software is good at generating reverse
On 1/3/08, Scott Wood [EMAIL PROTECTED] wrote:
Grant Likely wrote:
On 1/3/08, Timur Tabi [EMAIL PROTECTED] wrote:
Grant Likely wrote:
Why not be a child of the i2c bus with a phandle to the ssi bus?
Because when I probe the SSI node, I want to know what the attached codec
is.
So
On Wed, Jan 02, 2008 at 05:07:50PM -0700, Mark A. Greer wrote:
From: Mark A. Greer [EMAIL PROTECTED]
Fix error in booting-without-of.txt that indicates that a node can inherit
its #address-cells and #size-cells definitions from its parent's parent.
This is not correct and the latest dtc
Hi Roland,
Just want to make sure you've seen this patch and if it looks ok for you.
Thanks
Nam
On Thursday 20 December 2007 15:06, Hoang-Nam Nguyen wrote:
This patch allows ehca to forward event client-reregister-required to
registered clients. Such one event is generated by the switch eg.
Paul, please include this in 2.6.25 if there are no objections.
This patch adds the hugepagesz boot-time parameter for ppc64. It lets
one pick the size for huge pages. The choices available are 64K and 16M
when the base page size is 4k. It defaults to 16M (previously the only
only choice) if
On Thu, Jan 03, 2008 at 12:23:08PM -0600, Timur Tabi wrote:
Mark Brown wrote:
To cover everything you'd need to be able to specify all the clocking
parameters, especially a PLL configuration, and also specify more than
one of each item. Even then you'd still have problems like...
The
On Thu, Jan 03, 2008 at 01:18:31PM -0600, Scott Wood wrote:
Grant Likely wrote:
Gah! Don't do that! Then you need to maintain both directions in the
dts file. Software is good at generating reverse mappings.
Software is, however, lousy at correctly wading through
poorly-structured
Signed-off-by: Scott Wood [EMAIL PROTECTED]
---
dtc-parser.y | 16 +---
srcpos.h |1 +
treesource.c |1 -
3 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/dtc-parser.y b/dtc-parser.y
index 002ea7f..ddb7f27 100644
--- a/dtc-parser.y
+++ b/dtc-parser.y
@@
Previously, only failure to parse caused the reading of the tree to fail;
semantic errors that called yyerror() but not YYERROR only emitted a message,
without signalling make to stop the build.
Signed-off-by: Scott Wood [EMAIL PROTECTED]
---
dtc-parser.y |2 ++
dtc.c|2 +-
dtc.h
Looking in the diretory dtc is invoked from is not very useful behavior.
As part of the code reorganization to implement this, I removed the
uniquifying of name storage -- it seemed a rather dubious optimization
given likely usage, and some aspects of it would have been mildly awkward
to
Scott Wood wrote:
Signed-off-by: Scott Wood [EMAIL PROTECTED]
---
dtc-parser.y | 16 +---
srcpos.h |1 +
treesource.c |1 -
3 files changed, 14 insertions(+), 4 deletions(-)
I forgot to tag them as such, but these are of course dtc patches and
not Linux patches.
On Thu, Jan 03, 2008 at 12:26:27PM -0600, Timur Tabi wrote:
Scott Wood wrote:
+static struct of_platform_driver ucc_uart_of_driver = {
+.owner = THIS_MODULE,
+.name = ucc_uart,
Maybe better fsl,ucc_uart?
fsl,qe-uart is defined by
On Thursday 03 January 2008, Jon Tollefson wrote:
Paul, please include this in 2.6.25 if there are no objections.
No objections to this version from me, just questions.
This patch adds the hugepagesz boot-time parameter for ppc64. It lets
one pick the size for huge pages. The choices
On Thu, Jan 03, 2008 at 09:40:57AM -0500, Paul Gortmaker wrote:
Here is a small patch to clean up the usage info and the error returns
for ftdump -- not sure what the future holds for ftdump vs. simply using
dtc -I dtb -O dts someblob.dtb ...
I expect ftdump to stay around for the forseeable
On Thu, Jan 03, 2008 at 12:46:23PM +0100, Jochen Friedrich wrote:
Hi David,
+/ {
+ model = unknown,dbox2; // boot wrapper fills in correct manufacturer
Probably better just to leave model out of the dts and let the
bootwrapper add it.
Unfortunately, dtc requires a model:
$ dtc
On Thu, Jan 03, 2008 at 12:16:19PM -0600, Timur Tabi wrote:
Mark Brown wrote:
The machine support code (fabric driver in PowerPC terms, I think?)
tells the core how everything is connected together by registering
devices representing the links (eg, I2S) between the codecs, CPU and
other
On Thu, Jan 03, 2008 at 08:14:53AM -0600, Jon Loeliger wrote:
So, like, the other day David Gibson mumbled:
I posted this one a while back, but I guess it dropped through the
cracks.
Yep, sorry.
There's also the patch I sent you quite a long time ago that
adds a clarifying readme
thanks, applied.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
56 matches
Mail list logo
