From: "David H. Lynch Jr." <dhlii@dlasys•net>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Kernel symbol version history
Date: Sun, 09 Dec 2007 11:41:29 -0500 [thread overview]
Message-ID: <475C1AB9.5040005@dlasys.net> (raw)
In-Reply-To: <200712051807.36357.jcd@tribudubois.net>
Thank you.
I made use of one of the linux cross reference sites.
Though unless I don't know how to effectively use them trying to
track the history of a function, typdef, define, ..
is not particularly easy using lxr.
Grant's sugestion with git was closer to what I was looking for -
except that in some instances
needed to go back farther than it would take me..
Jean-Christophe Dubois wrote:
> Hi David,
>
> You could try the various "linux cross reference" web site out there. It is
> not necessarily complete (some linux version might be missing) but it can be
> usefull to lookup if some symbols/define/typedef were available in a
> particular Linux version.
>
> Have a look there.
>
> http://free-electrons.com/community/kernel/lxr
>
> Regards
>
> JC
>
> On Wednesday 05 December 2007 17:17:25 David H. Lynch Jr. wrote:
>
>> This might be slightly OT here, but would anyone know where there
>> might be a reference that indicates at precisely what version a given
>> symbol either appeared or disappeared within the Linux kernel ?
>>
>> As an example if a driver is supposed to work for 2.6 and 2.4 and
>> uses sysfs, or cdev, or alloc_chr_dev_region or ...
>> How can one tell at what point that api or symbol appeared so that
>> the proper conditionals appear within the driver.
>>
>> The last one that bit me was I made a collection of casting changes
>> to address 64bit vs. 32bit targets, and found that using the C99 fixed
>> size types - uint32_t, ... made life much more pleasant, after putting
>> them I nobody else could build because uintptr_t did not appear until
>> 2.6.24, and I still have not figured out exactly when uint32_t etc.
>> appeared.
>>
>> I would think there ought to be some resource besides group memory
>> to look this up ?
>> Is there a way to use git to look back through the history of a
>> symbol rather than a file.
>>
>
>
>
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys•net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2007-12-09 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 16:17 Kernel symbol version history David H. Lynch Jr.
2007-12-05 16:49 ` Grant Likely
2007-12-05 17:07 ` Jean-Christophe Dubois
2007-12-09 16:41 ` David H. Lynch Jr. [this message]
2007-12-06 13:08 ` David Woodhouse
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=475C1AB9.5040005@dlasys.net \
--to=dhlii@dlasys$(echo .)net \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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