linux 2.6.21.7
where do serial 8250 port fill its membase and mapbase fileds in
system initializing ?
I found that , when calling do_initcalls---> serial8250_init >
platform_driver_register--->bus_for_each_dev, system found
an device of serial 8250, which has already fill the membase a
On Mon, 2010-06-21 at 01:27 +0800, wilbur.chan wrote:
> linux 2.6.21.7
>
> where do serial 8250 port fill its membase and mapbase fileds in
> system initializing ?
>
..
> So I am really confused with serial 8250
> initializingwhere do kernel apply membase and mapbase
> filed to
On Mon, Jun 21, 2010 at 10:42 AM, Song, Barry wrote:
>
>
>>-Original Message-
>>From: uclinux-dist-devel-boun...@blackfin.uclinux.org
>>[mailto:uclinux-dist-devel-boun...@blackfin.uclinux.org] On
>>Behalf Of Anton Vorontsov
>>Sent: Friday, June 18, 2010 9:32 PM
>>To: Barry Song
>>Cc: David
>-Original Message-
>From: uclinux-dist-devel-boun...@blackfin.uclinux.org
>[mailto:uclinux-dist-devel-boun...@blackfin.uclinux.org] On
>Behalf Of Anton Vorontsov
>Sent: Friday, June 18, 2010 9:32 PM
>To: Barry Song
>Cc: David Brownell; Artem Bityutskiy;
>linux-ker...@vger.kernel.org;
Since the decrementer and timekeeping code was moved over to using
the generic clockevents and timekeeping infrastructure, several
variables and functions have been obsolete and effectively unused.
This deletes them.
In particular, wakeup_decrementer() is no longer needed since the
generic code re
Currently it is possible for userspace to see the result of
gettimeofday() going backwards by 1 microsecond, assuming that
userspace is using the gettimeofday() in the VDSO. The VDSO
gettimeofday() algorithm computes the time in "xsecs", which are
units of 2^-20 seconds, or approximately 0.954 mic
Here's the test program I used to verify that the VDSO gettimeofday
and clock_gettime are giving correct results.
Paul.
/*
* Copyright 2010 Paul Mackerras , IBM.
*
* This program is free software; it may be used and redistributed
* under the terms of the GNU Public Licence, either version 2,
