Gordon Farquharson wrote:
> On 5/18/07, Marcus Better <[EMAIL PROTECTED]> wrote:
>> my NSLU2 (266 MHz) has a problem with timekeeping. I run ntp, but it
>> doesn't
>> help - the clock drifts at least fifteen minutes a day. Did I miss
>> something obvious? My kernel is 2.6.20-1-ixp4xx.
>
> I'll hav
Martin Michlmayr a écrit :
> * Riku Voipio <[EMAIL PROTECTED]> [2007-05-19 00:08]:
>> Well, for example the toolchain issues (fortran, java) are still in the
>
> The fortran bootstrap error got fixed in gcc SVN a few days ago.
FYI I am currently doing a test build including this patch. I have
rew
* Riku Voipio <[EMAIL PROTECTED]> [2007-05-19 00:08]:
> Well, for example the toolchain issues (fortran, java) are still in the
The fortran bootstrap error got fixed in gcc SVN a few days ago.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
Hi Rick
On 5/18/07, Rick Thomas <[EMAIL PROTECTED]> wrote:
If you're running Debian, you may be able to use the "tickadj"
command at boot time to fudge the value of the kernel variable
"tick" (the number of microseconds added to the system clock every 1/
HZ seconds when the RTC interrupt occur
Hi Marcus
On 5/18/07, Marcus Better <[EMAIL PROTECTED]> wrote:
my NSLU2 (266 MHz) has a problem with timekeeping. I run ntp, but it doesn't
help - the clock drifts at least fifteen minutes a day. Did I miss
something obvious? My kernel is 2.6.20-1-ixp4xx.
I'll have a look at this issue this w
On May 18, 2007, at 6:00 AM, Marcus Better wrote:
Hi,
my NSLU2 (266 MHz) has a problem with timekeeping. I run ntp, but
it doesn't
help - the clock drifts at least fifteen minutes a day. Did I miss
something obvious? My kernel is 2.6.20-1-ixp4xx.
Marcus
Marcus,
If you're running Debian,
> You know I luvs 'ya, so we can get all of this out into the open. Don't
> hold back anything, ok? :)
Well, my opnionion is that flaming is the best way to demotivate ;)
(about the armel port)
> ... seems to be pretty good. Maybe the internals aren't all that pretty
> (I haven't looked), but
Sorry...my error.
--George
On Friday 18 May 2007 03:40 pm, peter green wrote:
> > This type of message does not give me a warm and fuzzy feeling
> > that makes me
> > want to work on the Debian arm port.
>
> I'd just like to point out that you are addressing your critisism at the
> wrong person.
> This type of message does not give me a warm and fuzzy feeling
> that makes me
> want to work on the Debian arm port.
I'd just like to point out that you are addressing your critisism at the wrong
person. your reply seems to be directed at a message from a person replying to
me not to me.
Hello Peter,
This type of message does not give me a warm and fuzzy feeling that makes me
want to work on the Debian arm port.
Please think about, being considerate, being respectful and being
collaborative.
--George
On Friday 18 May 2007 09:48 am, Matthias Klose wrote:
> Peter Green write
Lennert:
You know I luvs 'ya, so we can get all of this out into the open. Don't
hold back anything, ok? :)
Lennert Buytenhek wrote:
The regular ARM port isn't in very good shape at all, and there is no
indication that armeb or armel would end up doing any better.
Maybe I'm confused
On Fri, May 18, 2007 at 09:51:17AM -0500, Bill Gatliff wrote:
> > This isn't directed towards you, but a general remark is that all
> > the talk about dropping arm as a release architecture over the last
> > couple of years (for reasons that seem mostly beyond my control),
> > and the resulting un
Matthias Klose wrote:
> Lennert Buytenhek writes:
>> On Fri, May 18, 2007 at 03:48:00PM +0200, Matthias Klose wrote:
>>
package:gcc-4.1
version:4.1.2-7
severity:serious
from the relavent buildd logs:
>>> Note, that the severity is not RC for 68k; I do not intend to fix
>>>
Lennert Buytenhek writes:
> On Fri, May 18, 2007 at 03:48:00PM +0200, Matthias Klose wrote:
>
> > > package:gcc-4.1
> > > version:4.1.2-7
> > > severity:serious
> > >
> > > from the relavent buildd logs:
> >
> > Note, that the severity is not RC for 68k; I do not intend to fix
> > that. Same fo
Lennert:
This isn't directed towards you, but a general remark is that all the
talk about dropping arm as a release architecture over the last couple
of years (for reasons that seem mostly beyond my control), and the
resulting uncertainty has definitely made most of my motivation to
work on the
On Fri, May 18, 2007 at 03:48:00PM +0200, Matthias Klose wrote:
> > package:gcc-4.1
> > version:4.1.2-7
> > severity:serious
> >
> > from the relavent buildd logs:
>
> Note, that the severity is not RC for 68k; I do not intend to fix
> that. Same for arm, and arm porters don't seem to care that
I've written a howto for attaching a USB keyboard and a cheap (if you buy an
old secondhand one) PDA to a Linksys NSLU2 (the slug), for use as a terminal.
It is on the Debian forums:
http://forums.debian.net/viewtopic.php?t=15072
This doesn't allow you to have a terminal while booting, only once
Peter Green writes:
> package:gcc-4.1
> version:4.1.2-7
> severity:serious
>
> from the relavent buildd logs:
Note, that the severity is not RC for 68k; I do not intend to fix
that. Same for arm, and arm porters don't seem to care that much, so
maybe we should drop arm as a release architecture?
Hi,
my NSLU2 (266 MHz) has a problem with timekeeping. I run ntp, but it doesn't
help - the clock drifts at least fifteen minutes a day. Did I miss
something obvious? My kernel is 2.6.20-1-ixp4xx.
Marcus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? C
19 matches
Mail list logo
