linux-apus-devel

Hardware Clock support in 2.4

[<fp...@zu...>]

Sorry, I can't supply patches (I would have to have them cleared by IBM first)
but I have managed to get hardware clock support in 2.4.

Do the following: look for the APUS #define in drivers/char/vt.c and copy
the respective chunks to the 2.4 vt.c, et voilà.

It is one #include (at the top) and some case xxx: in the middle.

Have fun.
-- 
Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4,
CH-8803 Rüschlikon/Switzerland, Tel.  +41-1-724-84-42  Fax.   +41-1-724-89-56
 Business email: fp...@zu...          Private email: pe...@he...
   The opinions expressed here are mine and not necessarily those of IBM.

Re: Hardware Clock support in 2.4

[Michel <da...@re...>]

Frank Petzold wrote:
> 
> Sorry, I can't supply patches (I would have to have them cleared by IBM
> first) but I have managed to get hardware clock support in 2.4.

Can't you do a CVS commit either?


> Do the following: look for the APUS #define in drivers/char/vt.c and copy
> the respective chunks to the 2.4 vt.c, et voilà.
> 
> It is one #include (at the top) and some case xxx: in the middle.
> 
> Have fun.

I'd call that a 'literate patch' :) Thanks.


Michel


-- 
It is easier to fix Unix than to live with NT.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: Hardware Clock support in 2.4

[<gri...@ps...>]

> Do the following: look for the APUS #define in drivers/char/vt.c and copy
> the respective chunks to the 2.4 vt.c, et voil_.

Umm.. Wasn't this the 'very, very wrong m68k approach', which has been 
intentionally dropped in 2.3.x/2.4?

I remember Jes commenting that Linus et al. wouldn't accept this any
longer and that the m68k (and thus APUS) clock handling should be 
converted to the way the other platforms work?

AFAIK there was nobody who cared enough to build the driver, so
it got dropped..

Same story as the serial port stuff..

								Bye, Arno.

-- 
PSINetworks Europe           Fax: +31-23-5699841 | One disk to rule them all,
Siriusdreef 34               Tel: +31-23-5699840 | One disk to bind them,
2132WT Hoofddorp+--------------------------------+ One disk to hold the files
The Netherlands |   *  Musical Interlude  *      | And in the darkness grind 'em
----------------+--------------------------------+------------------------------

 We say Retribution, We say Vengeance is bliss, We say Revolution,
 With a Cast-Iron fist!                  (Megadeth, 'The Disintegrators')

--------------------------------------------------------------------------------

Re: Hardware Clock support in 2.4

[Frank P. <fp...@zu...>]

On Wed, Aug 02, 2000 at 01:19:27PM +0200, Arno Griffioen wrote:
> > Do the following: look for the APUS #define in drivers/char/vt.c and copy
> > the respective chunks to the 2.4 vt.c, et voil_.
> 
> Umm.. Wasn't this the 'very, very wrong m68k approach', which has been 
> intentionally dropped in 2.3.x/2.4?

I guess so.

> I remember Jes commenting that Linus et al. wouldn't accept this any
> longer and that the m68k (and thus APUS) clock handling should be 
> converted to the way the other platforms work?
> 
> AFAIK there was nobody who cared enough to build the driver, so
> it got dropped..

I really do not care what Linus thinks in this case (I think he is right), I
just want a working solution. Without effort. Yeah, I know, this is the 
wrong attitude. But as long as this kludge works and there is no proper driver
I will use it.
-- 
Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4,
CH-8803 Rüschlikon/Switzerland, Tel.  +41-1-724-84-42  Fax.   +41-1-724-89-56
 Business email: fp...@zu...          Private email: pe...@he...
   The opinions expressed here are mine and not necessarily those of IBM.

Re: Hardware Clock support in 2.4

[Geert U. <ge...@li...>]

On Wed, 2 Aug 2000, Arno Griffioen wrote:
> > Do the following: look for the APUS #define in drivers/char/vt.c and copy
> > the respective chunks to the 2.4 vt.c, et voil_.
> 
> Umm.. Wasn't this the 'very, very wrong m68k approach', which has been 
> intentionally dropped in 2.3.x/2.4?
> 
> I remember Jes commenting that Linus et al. wouldn't accept this any
> longer and that the m68k (and thus APUS) clock handling should be 
> converted to the way the other platforms work?

It should indeed use /dev/rtc.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds