* Re: kernel sources?
@ 2000-01-15 17:28 Kevin D. Kissell
2000-01-15 20:06 ` information on getting up to speed Richard Dubrawsk
` (2 more replies)
0 siblings, 3 replies; 11+ messages in thread
From: Kevin D. Kissell @ 2000-01-15 17:28 UTC (permalink / raw)
To: Ralf Baechle, Geert Uytterhoeven; +Cc: Linux/MIPS
-----Original Message-----
From: Ralf Baechle <ralf@oss.sgi.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/MIPS <linux@cthulhu.engr.sgi.com>
Date: Saturday, January 15, 2000 1:56 AM
Subject: Re: kernel sources?
>On Thu, Jan 13, 2000 at 05:03:39PM +0100, Geert Uytterhoeven wrote:
>
>> I used the R5000 CP0_COUNTER/CP0_COMPARE registers for the timer interrupt. I
>> know it's not accurate, but it's better than nothing. I still have to figure
>> out how more complex interrupts work in the MIPS source tree.
>
>It is accurate as driven by the CPU's clock. It is just somewhat tricky to
>handle and even more tricky on some broken CPUs. From an old email written
>by Bill Earl:
>
>[...]
>As far as I know, all R4000 processors, and possibly some R4400 processors,
>are affected. The bug is that, if you read $count exactly when it equals
>$compare, the count/compare interrupt for that count/compare crossing is
>discarded. The workaround from IRIX is appended. The variable
>r4000_clock_war is set to 1 if the system is an Indy with an R4000 processor.
>The r4k_compare_shadow is set to the same value as $compare whenever $compare
>is updated (with interrupts masked while the variable and $compare are
>updated together).
>[...]
There is also a race condition inherent in many implementations of
the timer interrupt handler, and the main stream of the current
MIPS/Linux distributions is no exception. The SGI code looks
a bit like this:
void indy_timer_interrupt(struct pt_regs *regs)
{
unsigned long count;
int irq = 7;
/* Ack timer and compute new compare. */
count = read_32bit_cp0_register(CP0_COUNT);
/* This has races. */
if ((count - r4k_cur) >= r4k_offset) {
/* If this happens to often we'll need to compensate. */
missed_heart_beats++;
r4k_cur = count + r4k_offset;
}
else
r4k_cur += r4k_offset;
ack_r4ktimer(r4k_cur);
kstat.irqs[0][irq]++;
do_timer(regs);
/* We update the Dallas time of day approx. every 11 minutes,
* because of how the numbers work out we need to make
* absolutely sure we do this update within 500ms before the
* next second starts, thus the following code.
*/
if ((time_status & STA_UNSYNC) == 0 &&
xtime.tv_sec > last_rtc_update + 660 &&
xtime.tv_usec >= 500000 - (tick >> 1) &&
xtime.tv_usec <= 500000 + (tick >> 1)) {
if (set_rtc_mmss(xtime.tv_sec) == 0)
last_rtc_update = xtime.tv_sec;
else
/* do it again in 60 s */
last_rtc_update = xtime.tv_sec - 600;
}
}
The inherent race is in the fact that the count is sampled
once at the beginnning of the routine and used throughout.
It is possible (with bad luck and sloppy drivers) to be very
late into the handler, so much so that the new time-out time
can be reached between the sample and the programming
of the compare register. If that happens, one gets no timer
interrupt for a full wrap of the count register. I first observed
this in OpenBSD, where the problem was worse, but Linux
has the same conceptual hole. A more robust handler
looks a bit like this:
void p5064_timer_interrupt(struct pt_regs *regs)
{
int irq = 7;
if(r4k_offset != 0) {
do {
kstat.irqs[0][irq]++;
do_timer(regs);
/* Historical comment/code:
* RTC time of day s updated approx. every 11
* minutes. Because of how the numbers work out
* we need to make absolutely sure we do this update
* within 500ms before the * next second starts,
* thus the following code.
*/
if ((time_status & STA_UNSYNC) == 0
&& xtime.tv_sec > last_rtc_update + 660
&& xtime.tv_usec >= 500000 - (tick >> 1)
&& xtime.tv_usec <= 500000 + (tick >> 1))
if (set_rtc_mmss(xtime.tv_sec) == 0)
last_rtc_update = xtime.tv_sec;
else
/* do it again in 60 s */
last_rtc_update = xtime.tv_sec - 600;
r4k_cur += r4k_offset;
ack_r4ktimer(r4k_cur);
} while (((unsigned long)read_32bit_cp0_register(CP0_COUNT)
- r4k_cur) < 0x7fffffff);
} else ack_r4ktimer(0);
}
As Ralf says, it's very accurate *if* you have an accurate picture of
the CPU's clock frequency. The usual mechanism of measuring
the progress of the count register against elapsed time on a TOD
clock has been known to be inaccurate on some platforms due
to skew between the visibility to software and the actual timing
event, so be careful.
Kevin K.
__
Kevin D. Kissell
MIPS Technologies European Architecture Lab
kevink@mips.com
Tel. +33.4.78.38.70.67
FAX. +33.4.78.38.70.68
^ permalink raw reply [flat|nested] 11+ messages in thread* information on getting up to speed
2000-01-15 17:28 kernel sources? Kevin D. Kissell
@ 2000-01-15 20:06 ` Richard Dubrawsk
2000-01-16 1:20 ` kernel sources? Ralf Baechle
2000-01-16 12:32 ` Geert Uytterhoeven
2 siblings, 0 replies; 11+ messages in thread
From: Richard Dubrawsk @ 2000-01-15 20:06 UTC (permalink / raw)
To: linux
Hi all, I have just successfully installed the hardhat distro on 2 sgi
indy machines, and have been reading everything I can find to get up to
speed on the port. The web pages seem terribly out of date. Could you
point me to some information about the current state of things. I have
scanned the archive of this mailing list, but it is hard to get a feel for
things from such disjoint information.
I have been using linux since 1995, mostly on intel, and recently have
been maintinaing several LinuxPPC and UltraLinux machines. I would like
to assist in the SGI port as time permits. My first desire is updated
tools. According to what I can find, there is not currently recent enough
tools available to support the 2.2.x series of kernels, I assume that is
not correct since I see indication that people are running 2.2.x kernels.
wheree can I find the latest stable(?) (reasonably stable?) versions of
libraries and compilers, etc.
Thank you
Richard Dubrawski
University of Illinois
Urbana-Champaign
(web page: http://www.students.uiuc.edu/~dubrawsk/)
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernel sources?
2000-01-15 17:28 kernel sources? Kevin D. Kissell
2000-01-15 20:06 ` information on getting up to speed Richard Dubrawsk
@ 2000-01-16 1:20 ` Ralf Baechle
2000-01-16 12:32 ` Geert Uytterhoeven
2 siblings, 0 replies; 11+ messages in thread
From: Ralf Baechle @ 2000-01-16 1:20 UTC (permalink / raw)
To: Kevin D. Kissell; +Cc: Ralf Baechle, Geert Uytterhoeven, Linux/MIPS
On Sat, Jan 15, 2000 at 06:28:40PM +0100, Kevin D. Kissell wrote:
> As Ralf says, it's very accurate *if* you have an accurate picture of
> the CPU's clock frequency. The usual mechanism of measuring
> the progress of the count register against elapsed time on a TOD
> clock has been known to be inaccurate on some platforms due
> to skew between the visibility to software and the actual timing
> event, so be careful.
The only machine where we actually calibrate the CPU counter is the Indy
where due to a hardware bug we cannot use the external timers as source
of interrupts.
In fact the current Linux kernel would even panic if it ever would find
an Indy working as per spec ;-)
We could improve that meassurement by rounding to the nearest crystal
known to be used on IP22 CPU modules plus maybe add an eventual user /
xntpd suplied fudge factor for deviations of the exact crystal frequency.
Ralf
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: kernel sources?
2000-01-15 17:28 kernel sources? Kevin D. Kissell
2000-01-15 20:06 ` information on getting up to speed Richard Dubrawsk
2000-01-16 1:20 ` kernel sources? Ralf Baechle
@ 2000-01-16 12:32 ` Geert Uytterhoeven
2 siblings, 0 replies; 11+ messages in thread
From: Geert Uytterhoeven @ 2000-01-16 12:32 UTC (permalink / raw)
To: Kevin D. Kissell; +Cc: Ralf Baechle, Linux/MIPS
On Sat, 15 Jan 2000, Kevin D. Kissell wrote:
> >On Thu, Jan 13, 2000 at 05:03:39PM +0100, Geert Uytterhoeven wrote:
> >
> >> I used the R5000 CP0_COUNTER/CP0_COMPARE registers for the timer interrupt. I
> >> know it's not accurate, but it's better than nothing. I still have to figure
> >> out how more complex interrupts work in the MIPS source tree.
> >
> >It is accurate as driven by the CPU's clock. It is just somewhat tricky to
> >handle and even more tricky on some broken CPUs. From an old email written
> >by Bill Earl:
> >
> >[...]
> >As far as I know, all R4000 processors, and possibly some R4400 processors,
> >are affected. The bug is that, if you read $count exactly when it equals
> >$compare, the count/compare interrupt for that count/compare crossing is
> >discarded. The workaround from IRIX is appended. The variable
> >r4000_clock_war is set to 1 if the system is an Indy with an R4000 processor.
> >The r4k_compare_shadow is set to the same value as $compare whenever $compare
> >is updated (with interrupts masked while the variable and $compare are
> >updated together).
> >[...]
>
> There is also a race condition inherent in many implementations of
> the timer interrupt handler, and the main stream of the current
> MIPS/Linux distributions is no exception. The SGI code looks
> a bit like this:
[...]
> The inherent race is in the fact that the count is sampled
> once at the beginnning of the routine and used throughout.
> It is possible (with bad luck and sloppy drivers) to be very
> late into the handler, so much so that the new time-out time
> can be reached between the sample and the programming
> of the compare register. If that happens, one gets no timer
> interrupt for a full wrap of the count register. I first observed
> this in OpenBSD, where the problem was worse, but Linux
> has the same conceptual hole. A more robust handler
> looks a bit like this:
I noticed this as well, especially if I put serial debug code in the interrupt
handler. Then it's safer to always reset count to 0 in the interrupt handler.
Of course it's very inaccurate then, but at least you keep on getting
interrupts in a reasonable time frame.
Now I'm using one of the timers in the host bridge to generate the actual timer
interrupt, which seems to work fine. I could also use the normal PC RTC, but
then I have to get the i8259 interrupts working first. Fortunately PCI
interrupts are handled by the host bridge as well, so I see no hurry in getting
the i8259 interrupts working too soon :-)
Gr{oetje,eeting}s,
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <Pine.LNX.4.05.10001130944010.3492-100000@callisto.of.borg>]
* Re: kernel sources?
[not found] <Pine.LNX.4.05.10001130944010.3492-100000@callisto.of.borg>
@ 2000-01-13 16:03 ` Geert Uytterhoeven
2000-01-14 11:32 ` Ralf Baechle
0 siblings, 1 reply; 11+ messages in thread
From: Geert Uytterhoeven @ 2000-01-13 16:03 UTC (permalink / raw)
To: Linux/MIPS
Hi,
As Ralf pointed out, my ELF loader problems were caused by the `-N' linker
option, triggering a bug in binutils 2.8.1.
FYI, I get until `Kernel panic: VFS: Unable to mount root fs' now.
I used the R5000 CP0_COUNTER/CP0_COMPARE registers for the timer interrupt. I
know it's not accurate, but it's better than nothing. I still have to figure
out how more complex interrupts work in the MIPS source tree.
Now we just have to do interrupts and PCI probing, and we're finished :-)
The board has the 16 standard i8259 interrupts, and 15 additional interrupts on
the host bridge. The i8259 is cascaded through one interrupt of the host
bridge, similar to the cascading through the OpenPIC on my CHRP board.
PCI is not connected to the i8259, but to the host bridge.
I can program the host bridge to map any interrupt to any of the CPU interrupts
(#0-#5 or NMI). I think the simplest way is to route them all through #0. Or do
you think it's better not to do that, and e.g. route the timer interrupt (after
I moved it from CP0_COUNTER/CP0_COMPARE to the PC style timer) to a different
interrupt? Instead of the PC style timer, I could also use the general purpose
timer in the host bridge.
Thx!
Gr{oetje,eeting}s,
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: kernel sources?
2000-01-13 16:03 ` Geert Uytterhoeven
@ 2000-01-14 11:32 ` Ralf Baechle
0 siblings, 0 replies; 11+ messages in thread
From: Ralf Baechle @ 2000-01-14 11:32 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Linux/MIPS
On Thu, Jan 13, 2000 at 05:03:39PM +0100, Geert Uytterhoeven wrote:
> I used the R5000 CP0_COUNTER/CP0_COMPARE registers for the timer interrupt. I
> know it's not accurate, but it's better than nothing. I still have to figure
> out how more complex interrupts work in the MIPS source tree.
It is accurate as driven by the CPU's clock. It is just somewhat tricky to
handle and even more tricky on some broken CPUs. From an old email written
by Bill Earl:
[...]
As far as I know, all R4000 processors, and possibly some R4400 processors,
are affected. The bug is that, if you read $count exactly when it equals
$compare, the count/compare interrupt for that count/compare crossing is
discarded. The workaround from IRIX is appended. The variable
r4000_clock_war is set to 1 if the system is an Indy with an R4000 processor.
The r4k_compare_shadow is set to the same value as $compare whenever $compare
is updated (with interrupts masked while the variable and $compare are
updated together).
[...]
Just calibrating the internal timer's value 100% exact is somewhat tricky.
The code used by the Indy generates a value that is somewhat off the
theoretical value. In practice I think it may be a good idea to meassure
the clock rate, the round it to the nearest frequency that is known to
be used with that system. Like rounding meassured 151MHz to 150MHz.
As for the time sources I think you best use a two-timer based scheme as
Intel or the Cobalt Qube 1/2. That will give you the low overhead of the
internal timer combined with the (hopefully!) higher precission of the
external timer.
> Now we just have to do interrupts and PCI probing, and we're finished :-)
>
> The board has the 16 standard i8259 interrupts, and 15 additional interrupts
> on the host bridge. The i8259 is cascaded through one interrupt of the host
> bridge, similar to the cascading through the OpenPIC on my CHRP board.
> PCI is not connected to the i8259, but to the host bridge.
>
> I can program the host bridge to map any interrupt to any of the CPU
> interrupts (#0-#5 or NMI). I think the simplest way is to route them all
> through #0. Or do you think it's better not to do that, and e.g. route the
> timer interrupt (after I moved it from CP0_COUNTER/CP0_COMPARE to the PC
> style timer) to a different interrupt? Instead of the PC style timer, I
> could also use the general purpose timer in the host bridge.
What you want to do is to optimize the whole thing for the least interrupt
overhead. An uncached read from the bridge chip is probably reasonably fast
but polling c0_cause is faster. Given that the best thing to do will depend
on how many interrupts from what device you expect. In any case you should
consider that the i8259 is supposed to be slow even though I guess that's no
longer correct for modern implementations. Also the timer interrupt will
have to be the highest priority interrupt or you may deadlock, so your
arrangements should to ensure that this will be easy.
Ralf
^ permalink raw reply [flat|nested] 11+ messages in thread
* kernel sources?
@ 2000-01-11 9:53 Geert Uytterhoeven
2000-01-11 18:47 ` Harald Koerfgen
0 siblings, 1 reply; 11+ messages in thread
From: Geert Uytterhoeven @ 2000-01-11 9:53 UTC (permalink / raw)
To: linux
Hi,
We are considering porting Linux to a R5000-based board.
I built a cross-compiler according to the guidelines in the MIPS-HOWTO and it
was a piece of cake.
Now I'm wondering which kernel sources you suggest to start a port with. I
tried the one from :pserver:cvs@linus.linux.sgi.com:/cvs (2.3.21) but
compilation stopped due to a problem in serial.c (I compiled for
CONFIG_ACER_PICA_61, just to see whether the tree worked).
Thanks in advance!
Gr{oetje,eeting}s,
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 11+ messages in thread* RE: kernel sources?
2000-01-11 9:53 Geert Uytterhoeven
@ 2000-01-11 18:47 ` Harald Koerfgen
2000-01-12 8:57 ` Geert Uytterhoeven
2000-01-12 16:19 ` Geert Uytterhoeven
0 siblings, 2 replies; 11+ messages in thread
From: Harald Koerfgen @ 2000-01-11 18:47 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: linux
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Hi Geert,
On 11-Jan-00 Geert Uytterhoeven wrote:
> We are considering porting Linux to a R5000-based board.
Just beeing curious, what board?
> Now I'm wondering which kernel sources you suggest to start a port with. I
> tried the one from :pserver:cvs@linus.linux.sgi.com:/cvs (2.3.21) but
> compilation stopped due to a problem in serial.c (I compiled for
> CONFIG_ACER_PICA_61, just to see whether the tree worked).
This source tree as absolutely correct to start with. The attached patch should
fix the complilation problem.
---
Regards,
Harald
[-- Attachment #2: serial-patch --]
[-- Type: text/plain, Size: 301 bytes --]
--- /nfs/cvs/linux-2.3/linux/include/asm-mips/serial.h Thu Aug 27 00:40:50 1998
+++ linux-idt/include/asm-mips/serial.h Wed Jan 5 21:09:20 2000
@@ -38,6 +38,9 @@
#define ACCENT_FLAGS 0
#define BOCA_FLAGS 0
#define HUB6_FLAGS 0
+#define RS_TABLE_SIZE 64
+#else
+#define RS_TABLE_SIZE
#endif
/*
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: kernel sources?
2000-01-11 18:47 ` Harald Koerfgen
@ 2000-01-12 8:57 ` Geert Uytterhoeven
2000-01-13 0:20 ` Ralf Baechle
2000-01-12 16:19 ` Geert Uytterhoeven
1 sibling, 1 reply; 11+ messages in thread
From: Geert Uytterhoeven @ 2000-01-12 8:57 UTC (permalink / raw)
To: Harald Koerfgen; +Cc: linux
On Tue, 11 Jan 2000, Harald Koerfgen wrote:
> > Now I'm wondering which kernel sources you suggest to start a port with. I
> > tried the one from :pserver:cvs@linus.linux.sgi.com:/cvs (2.3.21) but
> > compilation stopped due to a problem in serial.c (I compiled for
> > CONFIG_ACER_PICA_61, just to see whether the tree worked).
>
> This source tree as absolutely correct to start with. The attached patch should
> fix the complilation problem.
Thanks! But unfortunately it doesn't fix all problems:
serial.c: In function `line_info':
serial.c:3078: warning: long unsigned int format, unsigned int arg (arg 5)
serial.c: In function `autoconfig':
serial.c:3430: `ASYNC_IOC3' undeclared (first use this function)
serial.c:3430: (Each undeclared identifier is reported only once
serial.c:3430: for each function it appears in.)
serial.c: In function `rs_init':
serial.c:3999: `ASYNC_IOC3' undeclared (first use this function)
serial.c:4015: warning: long unsigned int format, unsigned int arg (arg 4)
I think some #ifdef CONFIG_SGI_IP27/#endif is missing there.
Gr{oetje,eeting}s,
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: kernel sources?
2000-01-12 8:57 ` Geert Uytterhoeven
@ 2000-01-13 0:20 ` Ralf Baechle
0 siblings, 0 replies; 11+ messages in thread
From: Ralf Baechle @ 2000-01-13 0:20 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Harald Koerfgen, linux
On Wed, Jan 12, 2000 at 09:57:41AM +0100, Geert Uytterhoeven wrote:
> Thanks! But unfortunately it doesn't fix all problems:
>
> serial.c: In function `line_info':
> serial.c:3078: warning: long unsigned int format, unsigned int arg (arg 5)
> serial.c: In function `autoconfig':
> serial.c:3430: `ASYNC_IOC3' undeclared (first use this function)
> serial.c:3430: (Each undeclared identifier is reported only once
> serial.c:3430: for each function it appears in.)
> serial.c: In function `rs_init':
> serial.c:3999: `ASYNC_IOC3' undeclared (first use this function)
> serial.c:4015: warning: long unsigned int format, unsigned int arg (arg 4)
>
> I think some #ifdef CONFIG_SGI_IP27/#endif is missing there.
Thanks for reporting! What's actually missing is the definition of this
flag in include/linux/serial.h.
Ralf
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: kernel sources?
2000-01-11 18:47 ` Harald Koerfgen
2000-01-12 8:57 ` Geert Uytterhoeven
@ 2000-01-12 16:19 ` Geert Uytterhoeven
1 sibling, 0 replies; 11+ messages in thread
From: Geert Uytterhoeven @ 2000-01-12 16:19 UTC (permalink / raw)
To: linux
Hi again,
First of all I would like to thank everyone who replied to my question!
In the mean time I managed to get until setup_arch() (which is after the
printing of the Linux banner :-). However, I'm seeing some very weird things: I
had to #if 0/#endif all code in setup_arch() starting with `strncpy
(command_line, arcs_cmdline, CL_SIZE);', or the system crashes right after
Loading R4000 MMU routines
(yes, this is before setup_arch()!).
I suspect the ELF loader in PMON to be buggy. I also had to disable all __init
stuff before, because functions marked __init ended up as all `nop' after
tftpboot.
I thought PMON may have problems with large images, so I disabled some more
config options for stuff I don't need at this stage, but now the #if 0/#endif
trick no longer works neither :-(
Note that I now know I can see `in advance' whether an image will work or not
(read: suffers from the above problem): PMON seems to coalesce two sections
when things go wrong.
Loading a working image using tftpboot:
Loading elf file: xxx.yyy.zzz.qqq:geert/vmlinux
0x80080000/1101820 + 0x8018e000/90656 + 0x801a4220/352320 + 2097 syms/
Entry address is 80080580
Loading a non-working image using tftpboot:
Loading elf file: xxx.yyy.zzz.qqq:geert/vmlinux
0x80080000/1192432 + 0x801a31f0/352400 + 2097 syms/
Entry address is 80080580
`objdump --headers' or `objdump --disassemble-all' don't show anything
suspicious.
I'm using gcc version egcs-2.90.27 980315 (egcs-1.0.2 release) and binutils
version 2.8.1 (mipsel-linux), using BFD version 2.8.1, compiled as crossutils
under Solaris/SPARC from binutils-2.8.1-2.src.rpm and egcs-1.0.2-9.src.rpm.
Anyone with a clue? Thx!
Gr{oetje,eeting}s,
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2000-01-16 12:46 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-01-15 17:28 kernel sources? Kevin D. Kissell
2000-01-15 20:06 ` information on getting up to speed Richard Dubrawsk
2000-01-16 1:20 ` kernel sources? Ralf Baechle
2000-01-16 12:32 ` Geert Uytterhoeven
[not found] <Pine.LNX.4.05.10001130944010.3492-100000@callisto.of.borg>
2000-01-13 16:03 ` Geert Uytterhoeven
2000-01-14 11:32 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2000-01-11 9:53 Geert Uytterhoeven
2000-01-11 18:47 ` Harald Koerfgen
2000-01-12 8:57 ` Geert Uytterhoeven
2000-01-13 0:20 ` Ralf Baechle
2000-01-12 16:19 ` Geert Uytterhoeven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox