On Mon, Jun 04, 2007 at 11:35:18AM +0200, Tino Keitel wrote: (By the way, it helps if you Cc: me - it's easy to lose track of things in the LKML noise) > Here it is: > > state = active > io 0x70-0x77 > options Yes, there's no IRQ listed. Can you try current git? -- Matthew Garrett | [email protected] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: RTC_DRV_CMOS can break userspace interface
- From: Tino Keitel <[email protected]>
- Re: RTC_DRV_CMOS can break userspace interface
- References:
- Re: RTC_DRV_CMOS can break userspace interface
- From: David Brownell <[email protected]>
- Re: RTC_DRV_CMOS can break userspace interface
- From: Tino Keitel <[email protected]>
- Re: RTC_DRV_CMOS can break userspace interface
- From: Matthew Garrett <[email protected]>
- Re: RTC_DRV_CMOS can break userspace interface
- From: Tino Keitel <[email protected]>
- Re: RTC_DRV_CMOS can break userspace interface
- From: Matthew Garrett <[email protected]>
- Re: RTC_DRV_CMOS can break userspace interface
- From: Tino Keitel <[email protected]>
- Re: RTC_DRV_CMOS can break userspace interface
- Prev by Date: Re: [PATCH] Fix roundup_pow_of_two(1)
- Next by Date: [PATCH -mm] Fix /proc/slab_allocators re seq_list_next() conversion
- Previous by thread: Re: RTC_DRV_CMOS can break userspace interface
- Next by thread: Re: RTC_DRV_CMOS can break userspace interface
- Index(es):
 |