All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Bottelberger <tjelfe@sigon.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: Linux on Amiga A600, a success story (in progress, with possible patch)
Date: Thu, 26 Jan 2012 18:05:53 +0100	[thread overview]
Message-ID: <97e6cf2ca60c81874f6ea82e8b4af158@localhost> (raw)
In-Reply-To: <4F2053C9.3090201@sigon.net>


Hi Geert,

On Wed, 25 Jan 2012 20:11:05 +0100, Patrick Bottelberger
<patrick.bottelberger@sigon.net> wrote:
> After activating CONFIG_RTC_CLASS and CONFIG_RTC_DRV_MSM6242 in the
> kernel and finally being able to get the device nodes created
> automatically by udev, the RTC now works... somewhat. 8 out of 10 reads
> from the RTC (via hctosys inside the kernel at startup, hwclock from
> userspace or cat one of the special files inside /sys/class/rtc) return
> successfully, but the other 2 return an ioctl()-error. I forgot which
> exactly, i'll go upstairs to the Amiga later and write it down.
> 

The error reported by hwclock is:
RTC_RD_TIME: Illegal Argument
ioctl() to /dev/rtc0 to read the time failed.

If reading /sys/class/rtc/rtc0/time with cat, the error is:
cat: /sys/class/rtc/rtc0/time: Invalid Argument

Additional to that, the date seems to be correct every time i read it (for
example with "cat /sys/class/rtc/rtc0/date"), but the time seems to be a
bit strange. Even if the time can be read, i get different times from the
clock. 3 cat's in a row returned:
02:04:16
12:04:18
22:04:19

That seems a bit... odd. Any ideas?

> The PCMCIA-network still doesn't work, i'll recompile the kernel with
> CONFIG_APNE=y (instead of m), maybe that will work.
> 

Still doesn't work, but i don't see anything PCMCIA-related in
/sys/{bus,bus/platform} either. I think that may be the problem, do i need
anything else besides of CONFIG_AMIGA_PCMCIA and CONFIG_APNE?

Maybe it's the debian patches that get everything out of order, i'll try
3.1.10 vanilla, maybe that'll work.


Regards,
Patrick

  reply	other threads:[~2012-01-26 17:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 18:37 Linux on Amiga A600, a success story (in progress, with possible patch) Patrick Bottelberger
2012-01-23 20:42 ` Geert Uytterhoeven
2012-01-23 23:04   ` Michael Schmitz
2012-01-24  8:41     ` Geert Uytterhoeven
2012-01-24 17:56     ` Patrick Bottelberger
2012-01-24 21:19       ` Geert Uytterhoeven
2012-01-27 17:44     ` Thorsten Glaser
2012-01-28 20:24       ` Michael Schmitz
2012-01-28 20:43         ` Thorsten Glaser
2012-01-28 20:49           ` Geert Uytterhoeven
2012-01-28 21:01             ` Thorsten Glaser
2012-01-24 17:35   ` Patrick Bottelberger
2012-01-24 21:17     ` Geert Uytterhoeven
2012-01-24 21:49       ` Geert Uytterhoeven
2012-01-25 19:11       ` Patrick Bottelberger
2012-01-26 17:05         ` Patrick Bottelberger [this message]
2012-02-07 19:55           ` Patrick Bottelberger
2012-02-07 22:13             ` Thorsten Glaser
2012-02-20 21:38               ` Patrick Bottelberger
2012-02-20 22:09                 ` Andreas Schwab
2012-02-20 22:47                   ` Patrick Bottelberger
2012-02-20 23:02                     ` Andreas Schwab
2012-02-21 10:55                       ` Patrick Bottelberger
2012-01-29 21:59         ` Geert Uytterhoeven

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=97e6cf2ca60c81874f6ea82e8b4af158@localhost \
    --to=tjelfe@sigon.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.