All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Ittershagen <lists@gate-nine.de>
To: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Changes to of_device ?
Date: Fri, 17 Jun 2011 14:57:53 +0200	[thread overview]
Message-ID: <4DFB4F51.1090509@gate-nine.de> (raw)
In-Reply-To: <201106171322.19067.dargaud@lpsc.in2p3.fr>

On 06/17/2011 01:22 PM, Guillaume Dargaud wrote:
>> Not answering your primary question here, but in order to print the most
>> recent tag (along with a uniqe suffix, see man page) that is reachable
>> from your current branch, you can use "git describe". It will print out
>> the kernel version on your latest Xilinx tree.
> 
> $ git describe
> v2.6.37-719-gecf08a4
> 
> $ cat ./include/linux/version.h
> #define LINUX_VERSION_CODE 132645
> #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
> 
> $ printf "%x\n" 132645
> 20625
> Something doesn't quite match here... 

It is hexadecimal. 0x25 = 37.

> But my original question about how do you declare a probe function in
> the latest kernels still stand...

The struct device_node was moved to struct device in order to make the
CONFIG_OF more generic. See

commit d706c1b050274b3bf97d7cb0542c0d070c9ccb8b
Author: Grant Likely <grant.likely@secretlab.ca>
Date:   Tue Apr 13 16:12:28 2010 -0700

    driver-core: Add device node pointer to struct device


Hope this helps,

  Philipp

  reply	other threads:[~2011-06-17 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17  9:19 Changes to of_device ? Guillaume Dargaud
2011-06-17 10:55 ` Philipp Ittershagen
2011-06-17 11:22   ` Guillaume Dargaud
2011-06-17 12:57     ` Philipp Ittershagen [this message]
2011-06-17 13:06       ` Philipp Ittershagen
2011-06-17 13:53         ` Guillaume Dargaud
2011-06-17 14:08           ` Grant Likely
2011-06-17 14:23             ` David Laight

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=4DFB4F51.1090509@gate-nine.de \
    --to=lists@gate-nine.de \
    --cc=dargaud@lpsc.in2p3.fr \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.