Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Riccardo <riccardo@kaffe.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Finn Thain <fthain@telegraphics.com.au>, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] reinstate mac rtc
Date: Wed, 15 Oct 2008 23:41:05 +0200	[thread overview]
Message-ID: <F86D8C33-9B01-11DD-B097-00050249ADE1@kaffe.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0810132114590.6220@anakin>

Finn, Geert,

so there is hope of not having a screwed clock time on my IIfx / QUadra 
950? the 2.2 series kernel had the clock, but no later kernel ever had 
it.


Generally, do you have a kernel to use on the above machines? I sitll 
have 2.2 but I can't upgrade libc due to that and this is breaking my 
upgrades and made my box a mess...



Riccardo
On Monday, October 13, 2008, at 09:21  PM, Geert Uytterhoeven wrote:

> 	Hi Finn,
>
> Thanks, I've added:
>     [PATCH] reinstate mac rtc
>     [PATCH] mac via cleanup and commentry
>     [PATCH] machw.h cleanup
>     [PATCH] mac baboon interrupt enable/disable
>     [PATCH] mac_esp asm fix
>     [PATCH] macfb annotations and compiler warning fix
>     [PATCH] fix trigraph ignored warning in setox.S
>     [PATCH] fbcon: remove broken mac vbl handler
>     [PATCH] mac_esp: fix for quadras with two esp chips
>     [PATCH] m68k: Do not overflow fb_fix_screeninfo.id in macfb
>
> Any of these I should still try to get into 2.6.28? Or is queueing for 
> 2.6.29
> OK?
>


  parent reply	other threads:[~2008-10-15 21:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0810061855300.28882@loopy.telegraphics.com.au>
2008-10-13 19:21 ` [PATCH] reinstate mac rtc Geert Uytterhoeven
2008-10-14  2:16   ` Finn Thain
2008-10-14  7:30     ` Geert Uytterhoeven
2008-10-15 21:41   ` Riccardo [this message]
2008-10-16  1:02     ` Finn Thain
2008-10-16  6:49       ` Brad Boyer
2008-10-18 11:12         ` Riccardo
2008-10-18 17:39           ` Kolbjørn Barmen
2008-10-19  2:53             ` Finn Thain
2008-10-19 16:37               ` Kolbjørn Barmen
2008-10-20  2:03                 ` Finn Thain
2008-10-20  2:05                 ` Michael Schmitz
2008-10-20 19:13                   ` Laurent Vivier
2008-10-22  7:19                     ` Michael Schmitz
2008-10-22 11:09                       ` Kolbjørn Barmen
2008-10-22 22:14                         ` Laurent Vivier
2008-10-23  3:56                           ` Michael Schmitz
2008-10-23  7:28                             ` Geert Uytterhoeven
2008-10-23  7:39                               ` Geert Uytterhoeven
2008-10-24  2:49                                 ` Michael Schmitz
2008-10-25  4:24                               ` Michael Schmitz
2008-10-25  5:10                                 ` Finn Thain
2008-10-25  7:08                                   ` Finn Thain
2008-10-26  3:04                                   ` Michael Schmitz
2008-10-26  3:24                                     ` Finn Thain
2008-10-19 11:52           ` Finn Thain
2008-10-18 16:17       ` Riccardo

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=F86D8C33-9B01-11DD-B097-00050249ADE1@kaffe.org \
    --to=riccardo@kaffe.org \
    --cc=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@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