public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: JWP <elseifthen@gmx.com>
To: kerolasa@gmail.com
Cc: Karel Zak <kzak@redhat.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: RFC hwclock: refactoring
Date: Sun, 23 Nov 2014 20:54:59 -0500	[thread overview]
Message-ID: <54728FF3.2020600@gmx.com> (raw)
In-Reply-To: <CAG27Bk1cCo_S0txKeFtAb3+oEQn9k24h9Ty7+E++Oxg93pVeQA@mail.gmail.com>

On 11/23/2014 10:32 AM, Sami Kerola wrote:
>> On 23 November 2014 at 13:31, Sami Kerola <kerolasa@iki.fi> wrote:
>>> On 22 November 2014 at 21:20, JWP <elseifthen@gmx.com> wrote:
>>> So, I noticed when *fdisk were rewritten that some antiquated
>>> code was dropped.  I would like some opinions on whether this
>>> should be done when refactoring hwclock.
>>>
>>> For example, do we need a workaround for the 1994 Award BIOS
>>> bug?
>>
>> I agree with Benno, it is time to say goodbye to that code.
>>
>>> Do we need Alpha code?  Is there a Linux distro that
>>> still officially supports Alpha machines?
>>
>> I'm not sure if there is any up to date distribution for Alpha. Kernel
>> crew seems to still care alpha, so it is not completely dead.
>>
>> http://marc.info/?t=140518903000002&r=1&w=2
>>
>> Maybe the question should be rephrased. How about dropping the Alpha
>> cmos support? It looks like Alpha has rtc support.


I intentionally did not include --directisa and hwclock-cmos.c in my
RFC, because my current position is that I2C access should remain in
hwclock for troubleshooting and testing purposes.

Your marc.info link seems to be broken.

>>
>> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/alpha/kernel/rtc.c
>>
>>> Any other ideas regarding this topic are welcome.
>>
>> Removal of i386 references should be safe.
>>
>> http://news.softpedia.com/news/Linux-Kernel-3-8-Says-Goodbye-to-i386-314293.shtml
>>
>> Since there is no other than Alpha & i386 references to cmos code, all
>> of it is subject for removal.

The __i386__ macro is set for all x86 platforms. They all support the ISA
architecture and therefore can use direct access methods to the persistent
clock.  That includes x86_64, even though the current iteration of hwclock
does not allow it, which is one of many hwclock bugs I will be fixing.


> 
> JWP,
> 
> It's a rainy day here, so I decided to make initial attempt to remove
> cmos & --badyear. Maybe something like these are what you are thinking
> of.
> 
> https://github.com/kerolasa/lelux-utiliteetit/commit/fa8825f77996dfad39bd09240729287706f6e72f
> https://github.com/kerolasa/lelux-utiliteetit/commit/74edf1aa9c16d351e9fdb25a961ec1932c60c674
> 
> After a clean up like that there is still tons to do. For example this
> snippet here
> 
> /*
>  * struct rtc_time is present since 1.3.99.
>  * Earlier (since 1.3.89), a struct tm was used.
>  */
> 
> is screaming obsolete.
> 

All of the code will be changing, Karel ask me to refactor it outside
of the main development channel.  I wanted to see if the Alpha and 
Award code was somehow important to someone.  My opinion is to remove
it, but maybe there is something I am unaware of.

Even the source for the aboot Alpha boot-loader, and the previous center
of all things Linux-Alpha, alphalinux.org is gone.

I do wonder why the kernel hasn't dropped it yet though.

I'm curious as to what Mr. Z's thoughts are going to be.

Thanks for your time and input Sami!

  reply	other threads:[~2014-11-24  1:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 21:20 RFC hwclock: refactoring JWP
2014-11-23 10:27 ` Benno Schulenberg
2014-11-24  1:56   ` JWP
2014-11-23 13:31 ` Sami Kerola
2014-11-23 15:32   ` Sami Kerola
2014-11-24  1:54     ` JWP [this message]
2014-11-24 10:14       ` Karel Zak
2015-02-16  9:02   ` Mike Frysinger
2015-02-16 11:37     ` J William Piggott
2015-02-16 12:32       ` Mike Frysinger

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=54728FF3.2020600@gmx.com \
    --to=elseifthen@gmx.com \
    --cc=kerolasa@gmail.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox