On 23 February 2010 23:19, Sebastian Reichel wrote:
>
> I just tried the patch and it seems to work. It will be included in the
> next Debian kernel.
OK, cool, thanks. (Wow, my first ever kernel patch!)
Neil
___
Openmoko community mailing list
c
On Tue, Feb 23, 2010 at 10:40:26PM +, Neil Jerram wrote:
> On 23 February 2010 18:18, Sebastian Reichel wrote:
> >
> > Hi,
> >
> > what happened with this patch? My FR ran out of power, which
> > resulted in a reset RTC. Now I can't set it back to current time,
> > because of hwclock's read.
>
On 23 February 2010 18:18, Sebastian Reichel wrote:
>
> Hi,
>
> what happened with this patch? My FR ran out of power, which
> resulted in a reset RTC. Now I can't set it back to current time,
> because of hwclock's read.
I wasn't able to test it myself, because I don't have a
cross-compilation s
On Sun, Jan 24, 2010 at 06:04:02PM +, Neil Jerram wrote:
> 2010/1/24 Andy Poling :
> >
> > I finally looked into it, and this is the problem (with RTC debugging
> > enabled): [...]
>
> Wow, what a fantastic bug! So, IIUC, it will only strike someone who
> upgraded in January from a kernel wit
2010/1/24 Andy Poling :
>
> I finally looked into it, and this is the problem (with RTC debugging
> enabled): [...]
Wow, what a fantastic bug! So, IIUC, it will only strike someone who
upgraded in January from a kernel without Werner's change, to one with
Werner's change - because the old kernel
On Mon, 18 Jan 2010, Neil Jerram wrote:
> One more possible issue with this kernel. The boot messages always say
>
> [21474539.53] pcf50633-rtc pcf50633-rtc: hctosys: unable to read
> the hardware clock
I'm seeing this on my build from a recent git pull as well. It also has the
unpleasant si
6 matches
Mail list logo
