Wolfgang Denk wrote on 2010/02/11 22:39:00:
>
> Dear Joakim Tjernlund,
>
> In message 005cf...@transmode.se> you wrote:
> >
> > > I have no idea how it is actually done in the kernel code... but gcc
> > > defines it:
> > >
> > > gcc -dM -E -x c - <<<'' | grep ENDIAN
> > > #define __BIG_ENDIAN__ 1
On Thu, Feb 11, 2010 at 3:12 PM, John Linn wrote:
> These changes add MDIO and phy lib support to the driver as the
> IP core now supports the MDIO bus.
>
> The MDIO bus and phy are added as a child to the emaclite in the device
> tree as illustrated below.
>
> mdio {
> #address-cells = <1>
In message <4b7481a6.7080...@gmx.de> you wrote:
> On 02/10/2010 06:31 AM, Michael Neuling wrote:
> > In message<20100210141016.4d18.a69d9...@jp.fujitsu.com> you wrote:
> >>> On 02/09/2010 10:51 PM, Michael Neuling wrote:
> >> I'd still like someone with a CONFIG_STACK_GROWSUP arch to test/ACK
On 02/10/2010 06:31 AM, Michael Neuling wrote:
In message<20100210141016.4d18.a69d9...@jp.fujitsu.com> you wrote:
On 02/09/2010 10:51 PM, Michael Neuling wrote:
I'd still like someone with a CONFIG_STACK_GROWSUP arch to test/ACK it
as well.
There's only one CONFIG_GROWSUP arch - parisc.
Coul
These changes add MDIO and phy lib support to the driver as the
IP core now supports the MDIO bus.
The MDIO bus and phy are added as a child to the emaclite in the device
tree as illustrated below.
mdio {
#address-cells = <1>;
#size-cells = <0>;
phy0: p...@7 {
Dear Joakim Tjernlund,
In message
you
wrote:
>
> > I have no idea how it is actually done in the kernel code... but gcc
> > defines it:
> >
> > gcc -dM -E -x c - <<<'' | grep ENDIAN
> > #define __BIG_ENDIAN__ 1
> > #define _BIG_ENDIAN 1
>
> That doesn't define __BYTE_ORDER. Try the same gcc co
> -Original Message-
> From: glik...@secretlab.ca [mailto:glik...@secretlab.ca] On Behalf Of Grant
> Likely
> Sent: Thursday, February 11, 2010 2:16 PM
> To: John Linn
> Cc: net...@vger.kernel.org; linuxppc-...@ozlabs.org; jgar...@pobox.com;
> jwbo...@linux.vnet.ibm.com;
> john.willi...@p
On Thu, Feb 11, 2010 at 1:52 PM, John Linn wrote:
> These changes add MDIO and phy lib support to the driver as the
> IP core now supports the MDIO bus.
>
> The MDIO bus and phy are added as a child to the emaclite in the device
> tree as illustrated below.
>
> mdio {
> #address-cells = <1>
These changes add MDIO and phy lib support to the driver as the
IP core now supports the MDIO bus.
The MDIO bus and phy are added as a child to the emaclite in the device
tree as illustrated below.
mdio {
#address-cells = <1>;
#size-cells = <0>;
phy0: p...@7 {
Hello,
I use a 82xx platform with a device tree which describes 4 SCC ports.
I want to probe these 4 SCC ports against 2 serial drivers (e.g. async and
sync).
Each port is declared as compatible with the 2 drivers.
When the first driver is loaded, all devices are probed and bound
with this drive
Adrian Reber wrote on 2010/02/11 17:33:29:
>
> On Thu, Feb 11, 2010 at 05:17:37PM +0100, Joakim Tjernlund wrote:
> > I am getting confused about on how to test for Endian in the kernel code.
> > In user
> > space one uses #if __BYTE_ORDER == __LITTLE_ENDIAN or #if __BYTE_ORDER ==
> > __BIG_ENDIA
Paul Mackerras wrote:
On Wed, Feb 10, 2010 at 06:06:10PM -0600, Scott Wood wrote:
Paul Mackerras wrote:
Some limitations:
- No threshold support -- need to figure out how to represent it in
the event struct from userspace.
What does "threshold support" mean in this context? Does it mean
som
Andreas Schwab wrote on 2010/02/11 17:35:54:
>
> Joakim Tjernlund writes:
>
> > I am getting confused about on how to test for Endian in the kernel code.
> > In user
> > space one uses #if __BYTE_ORDER == __LITTLE_ENDIAN or #if __BYTE_ORDER ==
> > __BIG_ENDIAN
> >
> > I can see lots of kernel h
On Thu, Feb 11, 2010 at 05:17:37PM +0100, Joakim Tjernlund wrote:
> I am getting confused about on how to test for Endian in the kernel code. In
> user
> space one uses #if __BYTE_ORDER == __LITTLE_ENDIAN or #if __BYTE_ORDER ==
> __BIG_ENDIAN
>
> I can see lots of kernel headers using this test
Joakim Tjernlund writes:
> I am getting confused about on how to test for Endian in the kernel code. In
> user
> space one uses #if __BYTE_ORDER == __LITTLE_ENDIAN or #if __BYTE_ORDER ==
> __BIG_ENDIAN
>
> I can see lots of kernel headers using this test too
Only outside of __KERNEL__.
Andrea
>
> I am getting confused about on how to test for Endian in the kernel code. In
> user
> space one uses #if __BYTE_ORDER == __LITTLE_ENDIAN or #if __BYTE_ORDER ==
> __BIG_ENDIAN
>
> I can see lots of kernel headers using this test too, but it doesn't seem
> to be an arch specific file #defining
I am getting confused about on how to test for Endian in the kernel code. In
user
space one uses #if __BYTE_ORDER == __LITTLE_ENDIAN or #if __BYTE_ORDER ==
__BIG_ENDIAN
I can see lots of kernel headers using this test too, but it doesn't seem
to be an arch specific file #defining __BYTE_ORDER.
17 matches
Mail list logo
