On Friday 30 March 2007 03:09:14 David Brownell wrote:
> On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
> > On Friday 30 March 2007 00:33:35 David Brownell wrote:
> > > On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
>
> > > > So the only way out is to emulate RTC using HPET,
>
On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
> On Friday 30 March 2007 00:33:35 David Brownell wrote:
> > On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> > > So the only way out is to emulate RTC using HPET,
> > > It is done this way in old rtc driver, rtc-cmos should do the
On Friday 30 March 2007 00:33:35 David Brownell wrote:
> On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> > On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
>
> > When HPET is active it eats RTC IRQ,
>
> Only when HPET timers 0 and 1 are set up for "Legacy Replacement Mode".
> In
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
> When HPET is active it eats RTC IRQ,
Only when HPET timers 0 and 1 are set up for "Legacy Replacement Mode".
In the more sensible "Standard Mode", they have their own IRQs.
>
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
When HPET is active it eats RTC IRQ,
Only when HPET timers 0 and 1 are set up for Legacy Replacement Mode.
In the more sensible Standard Mode, they have their own IRQs.
So
On Friday 30 March 2007 00:33:35 David Brownell wrote:
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
When HPET is active it eats RTC IRQ,
Only when HPET timers 0 and 1 are set up for Legacy Replacement Mode.
In the more
On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
On Friday 30 March 2007 00:33:35 David Brownell wrote:
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
So the only way out is to emulate RTC using HPET,
It is done this way in old rtc driver, rtc-cmos should do the same.
On Friday 30 March 2007 03:09:14 David Brownell wrote:
On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
On Friday 30 March 2007 00:33:35 David Brownell wrote:
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
So the only way out is to emulate RTC using HPET,
On Wednesday 28 March 2007 22:42:00 Linus Torvalds wrote:
>
> On Wed, 28 Mar 2007, David Brownell wrote:
> >
> > On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
> >
> > > It's a *device*, dammit. It should save and resume like one (probably as
> > > a
> > > system device). The
On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
> On Wednesday 28 March 2007 1:19 pm, Maxim wrote:
> > On Wednesday 28 March 2007 21:38:55 David Brownell wrote:
>
> > >
> > > Also, making HPET use the legacy mode seems like a step backwards.
>
> > It is not 'legacy' mode,
> > It
On Wednesday 28 March 2007 1:42 pm, Linus Torvalds wrote:
>
> I won't disagree - it might well be much nicer to just show it in the
> "real" device tree. I'm not 100% sure where in the tree it would go,
> though. It should probably be "inside" the root entry, before any of the
> PCI buses.
On Wednesday 28 March 2007 1:19 pm, Maxim wrote:
> On Wednesday 28 March 2007 21:38:55 David Brownell wrote:
> >
> > Also, making HPET use the legacy mode seems like a step backwards.
> It is not 'legacy' mode,
> It is a legacy replacement mode.
Typo, sorry.
> It this mode HPET takes
On Wed, 28 Mar 2007, David Brownell wrote:
>
> On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
>
> > It's a *device*, dammit. It should save and resume like one (probably as a
> > system device). The "set_mode()" etc stuff is at a completely different
> > (higher) conceptual level.
On Wednesday 28 March 2007 21:38:55 David Brownell wrote:
> On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
>
> > It's a *device*, dammit. It should save and resume like one (probably as a
> > system device). The "set_mode()" etc stuff is at a completely different
> > (higher)
On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
> It's a *device*, dammit. It should save and resume like one (probably as a
> system device). The "set_mode()" etc stuff is at a completely different
> (higher) conceptual level.
Agreed, except about "probably as a system device".
On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
It's a *device*, dammit. It should save and resume like one (probably as a
system device). The set_mode() etc stuff is at a completely different
(higher) conceptual level.
Agreed, except about probably as a system device.
Last I
On Wednesday 28 March 2007 21:38:55 David Brownell wrote:
On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
It's a *device*, dammit. It should save and resume like one (probably as a
system device). The set_mode() etc stuff is at a completely different
(higher) conceptual level.
On Wed, 28 Mar 2007, David Brownell wrote:
On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
It's a *device*, dammit. It should save and resume like one (probably as a
system device). The set_mode() etc stuff is at a completely different
(higher) conceptual level.
Agreed,
On Wednesday 28 March 2007 1:19 pm, Maxim wrote:
On Wednesday 28 March 2007 21:38:55 David Brownell wrote:
Also, making HPET use the legacy mode seems like a step backwards.
It is not 'legacy' mode,
It is a legacy replacement mode.
Typo, sorry.
It this mode HPET takes over IRQ0
On Wednesday 28 March 2007 1:42 pm, Linus Torvalds wrote:
I won't disagree - it might well be much nicer to just show it in the
real device tree. I'm not 100% sure where in the tree it would go,
though. It should probably be inside the root entry, before any of the
PCI buses.
Mixing
On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
On Wednesday 28 March 2007 1:19 pm, Maxim wrote:
On Wednesday 28 March 2007 21:38:55 David Brownell wrote:
Also, making HPET use the legacy mode seems like a step backwards.
It is not 'legacy' mode,
It is a legacy
On Wednesday 28 March 2007 22:42:00 Linus Torvalds wrote:
On Wed, 28 Mar 2007, David Brownell wrote:
On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
It's a *device*, dammit. It should save and resume like one (probably as
a
system device). The set_mode() etc stuff is
22 matches
Mail list logo
