From cjb@netusa1.net Mon Mar 1 12:34:44 1999 Received: from gatem02.netusa1.net (gatem02.netusa1.net [205.139.170.9]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA20139; Mon, 1 Mar 1999 12:34:40 +0100 (MET) Received-Date: Mon, 1 Mar 1999 12:34:40 +0100 (MET) Received: from speedrcr.netusa1.net (indyi-141.netusa1.net [206.30.240.141]) by gatem02.netusa1.net (8.9.1/8.9.1) with SMTP id GAA14921 for ; Mon, 1 Mar 1999 06:34:12 -0500 (EST) (envelope-from cjb@netusa1.net) Message-Id: <3.0.5.32.19990301063832.007c9b40@mail.netusa1.net> X-Sender: cjb@mail.netusa1.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 01 Mar 1999 06:38:32 -0500 To: linux-mips@fnet.fr From: Marshall -n- Carol Subject: Anyone ever dealt with NeTpower Fastseries MP? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Length: 567 Lines: 14 Greetings to all. I was given a NeTpower Fastseries MP by a client who only uses NT (ack!). I am determined to get Linux running on the box but am having trouble finding much info on it (NeTpower seems to have gone out of business). I must admit I am not currently a programmer or developer but am eager to do whatever I need to get this running. Has anyone had any experience with this box or know where I might get more info? Please forward any replies to my email below. TIA, Marshall Radwin Systems Analyst Data Communications Consulting radwinm@dccinc.com From Harald.Koerfgen@home.ivm.de Mon Mar 1 21:54:28 1999 Received: from aw.ivm.net (mail.ivm.net [62.204.1.4]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA24145; Mon, 1 Mar 1999 21:54:26 +0100 (MET) Received-Date: Mon, 1 Mar 1999 21:54:26 +0100 (MET) Received: from franz.no.dom (port59.koeln.ivm.de [195.247.239.59]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id VAA06765 for ; Mon, 1 Mar 1999 21:54:12 +0100 X-To: Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 01 Mar 1999 21:56:38 +0100 (MET) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: linux-mips@fnet.fr Subject: Linux/MIPS-2.2.1 Content-Length: 250 Lines: 11 Hi all, I have merged my source tree with the CVS once again. While writing this I am uploading linux-2.2.1-dec.tar.gz to ftp://ftp.linux.sgi.com/pub/linux/mips/test. No big news, just an update and minor changes :-). Have fun. --- Regards, Harald From ryan@end.org Thu Mar 4 01:40:04 1999 Received: from q7.q7.com (ryan@q7.q7.com [206.58.126.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA13783; Thu, 4 Mar 1999 01:40:02 +0100 (MET) Received-Date: Thu, 4 Mar 1999 01:40:02 +0100 (MET) Received: from localhost (ryan@localhost) by q7.q7.com (8.9.1/8.9.1) with SMTP id QAA13509 for ; Wed, 3 Mar 1999 16:39:51 -0800 (PST) Date: Wed, 3 Mar 1999 16:39:51 -0800 (PST) From: Ryan Sweet X-Sender: ryan@q7.q7.com To: linux-mips@fnet.fr Subject: spoofing the kenel header... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 681 Lines: 19 I am working on porting to a CE device that uses the r4300. It loads CE using tftp. I can feed it a linux kernel instead of the CE OS, but it chokes on a check that the bootprom does against a string that it expects in the header fo the file it is downloading. I can tweak the kernel with a binary editor, at which point it loads the image, but chokes because the checksum mismatches. Is there a way that I can specify a certain string be included in the kernel header from offset 000000 through offset 00012f? Can I do this int he src, or is there a way to do it in a binary editor and then spoof the checksum? thanks, -ryan Ryan Sweet ryan@end.org http://the.end.org/ryan From imp@harmony.village.org Thu Mar 4 07:38:44 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id HAA16042; Thu, 4 Mar 1999 07:38:39 +0100 (MET) Received-Date: Thu, 4 Mar 1999 07:38:39 +0100 (MET) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id GAA36259; Thu, 4 Mar 1999 06:38:24 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA27701; Wed, 3 Mar 1999 23:39:44 -0700 (MST) Message-Id: <199903040639.XAA27701@harmony.village.org> To: linux-mips@fnet.fr Cc: ryan@end.org Subject: Re: spoofing the kenel header... In-reply-to: Your message of "Wed, 03 Mar 1999 16:39:51 PST." References: Date: Wed, 03 Mar 1999 23:39:44 -0700 From: Warner Losh Content-Length: 22592 Lines: 785 In message Ryan Sweet writes: : Is there a way that I can specify a certain string be included in the : kernel header from offset 000000 through offset 00012f? Can I do this int : he src, or is there a way to do it in a binary editor and then spoof the : checksum? One way to do this is the same way that the NetBSD/OpenBSD folks have been dealing with the PECOFF/ECOFF issue for years. WinCE, like all the brain damaged windows on mips things before it, uses an extended coff. You may be able to use elf2ecoff which NetBSD and OpenBSD have in their trees. Alternatively, you could use objcopy, but I don't know if that works. I have some extremely preliminary patches to gcc/binutils which makes it produce PECOFF binaries. I'm still fighting some interesting relocation problems, as well as some other gotchas. Since my CE box died, I've been less motivated to work on it. elf2ecoff is short, and I've included it below. As you can see, it is written for NetBSD, but shouldn't be too hard to port to Linux. I use the following program all the time to boot OpenBSD kernels (which don't have a bootstrap loader, so need to be ecoff) all the time. It does assume that the Elf headers are on your system, which may or may not be the case for Linux. If it isn't the case, you can grab include files from ftp.netbsd.org or ftp.openbsd.org. Ralf likely has either objcopy working, or a working one of these... Warner /* $NetBSD: elf2ecoff.c,v 1.12 1999/01/11 22:40:00 kleink Exp $ */ /* * Copyright (c) 1997 Jonathan Stone * All rights reserved. * Copyright (c) 1995 * Ted Lemon (hereinafter referred to as the author) * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. The name of the author may not be used to endorse or promote products * derived from this software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. */ /* elf2ecoff.c This program converts an elf executable to an ECOFF executable. No symbol table is retained. This is useful primarily in building net-bootable kernels for machines (e.g., DECstation and Alpha) which only support the ECOFF object file format. */ #include #include #include #include #include #include #include #include #include #include #include #include #include /* Elf Program segment permissions, in program header flags field */ #define PF_X (1 << 0)/* Segment is executable */ #define PF_W (1 << 1)/* Segment is writable */ #define PF_R (1 << 2)/* Segment is readable */ #define PF_MASKPROC 0xF0000000 /* Processor-specific reserved bits */ #define ISLAST(p) (p->n_un.n_name == 0 || p->n_un.n_name[0] == 0) struct sect { unsigned long vaddr; unsigned long len; }; struct elf_syms { int nsymbols; Elf32_Sym *elf_syms; off_t stringsize; char *stringtab; }; struct ecoff_syms { int nsymbols; struct ecoff_extsym *ecoff_syms; off_t stringsize; char *stringtab; }; int debug = 0; int phcmp(Elf32_Phdr * h1, Elf32_Phdr * h2); char *saveRead(int file, off_t offset, off_t len, char *name); void safewrite(int outfile, void *buf, off_t len, const char *msg); void copy(int, int, off_t, off_t); void combine(struct sect * base, struct sect * new, int paddable); void translate_syms(struct elf_syms *, struct ecoff_syms *); void elf_symbol_table_to_ecoff(int out, int in, struct ecoff_exechdr * ep, off_t symoff, off_t symsize, off_t stroff, off_t strsize); int make_ecoff_section_hdrs(struct ecoff_exechdr * ep, struct ecoff_scnhdr * esecs); void write_ecoff_symhdr(int outfile, struct ecoff_exechdr * ep, struct ecoff_symhdr * symhdrp, long nesyms, long extsymoff, long extstroff, long strsize); void pad16(int fd, int size, const char *msg); int *symTypeTable; void elf_read_syms(struct elf_syms * elfsymsp, int infile, off_t symoff, off_t symsize, off_t stroff, off_t strsize); int main(int argc, char **argv, char **envp) { Elf32_Ehdr ex; Elf32_Phdr *ph; Elf32_Shdr *sh; char *shstrtab; int strtabix, symtabix; int i, pad; struct sect text, data, bss; /* a.out-compatible sections */ struct sect rdata, sdata, sbss; /* ECOFF-only sections */ struct ecoff_exechdr ep; struct ecoff_scnhdr esecs[6]; struct ecoff_symhdr symhdr; int infile, outfile; unsigned long cur_vma = ULONG_MAX; int symflag = 0; int nsecs = 0; text.len = data.len = bss.len = 0; text.vaddr = data.vaddr = bss.vaddr = 0; rdata.len = sdata.len = sbss.len = 0; rdata.vaddr = sdata.vaddr = sbss.vaddr = 0; /* Check args... */ if (argc < 3 || argc > 4) { usage: fprintf(stderr, "usage: elf2ecoff [-s]\n"); exit(1); } if (argc == 4) { if (strcmp(argv[3], "-s")) goto usage; symflag = 1; } /* Try the input file... */ if ((infile = open(argv[1], O_RDONLY)) < 0) { fprintf(stderr, "Can't open %s for read: %s\n", argv[1], strerror(errno)); exit(1); } /* Read the header, which is at the beginning of the file... */ i = read(infile, &ex, sizeof ex); if (i != sizeof ex) { fprintf(stderr, "ex: %s: %s.\n", argv[1], i ? strerror(errno) : "End of file reached"); exit(1); } /* Read the program headers... */ ph = (Elf32_Phdr *) saveRead(infile, ex.e_phoff, ex.e_phnum * sizeof(Elf32_Phdr), "ph"); /* Read the section headers... */ sh = (Elf32_Shdr *) saveRead(infile, ex.e_shoff, ex.e_shnum * sizeof(Elf32_Shdr), "sh"); /* Read in the section string table. */ shstrtab = saveRead(infile, sh[ex.e_shstrndx].sh_offset, sh[ex.e_shstrndx].sh_size, "shstrtab"); /* Read in the section string table. */ shstrtab = saveRead(infile, sh[ex.e_shstrndx].sh_offset, sh[ex.e_shstrndx].sh_size, "shstrtab"); /* Look for the symbol table and string table... Also map section * indices to symbol types for a.out */ symtabix = 0; strtabix = 0; for (i = 0; i < ex.e_shnum; i++) { char *name = shstrtab + sh[i].sh_name; if (!strcmp(name, ".symtab")) symtabix = i; else if (!strcmp(name, ".strtab")) strtabix = i; } /* Figure out if we can cram the program header into an ECOFF * header... Basically, we can't handle anything but loadable * segments, but we can ignore some kinds of segments. We can't * handle holes in the address space. Segments may be out of order, * so we sort them first. */ qsort(ph, ex.e_phnum, sizeof(Elf32_Phdr), (int (*) (const void *, const void *)) phcmp); for (i = 0; i < ex.e_phnum; i++) { /* Section types we can ignore... */ if (ph[i].p_type == Elf_pt_null || ph[i].p_type == Elf_pt_note || ph[i].p_type == Elf_pt_phdr || ph[i].p_type == Elf_pt_mips_reginfo) { if (debug) { fprintf(stderr, " skipping PH %d type %d flags 0x%x\n", i, ph[i].p_type, ph[i].p_flags); } continue; } /* Section types we can't handle... */ else if (ph[i].p_type != Elf_pt_load) { fprintf(stderr, "Program header %d type %d can't be converted.\n", i, ph[i].p_type); exit(1); } /* Writable (data) segment? */ if (ph[i].p_flags & PF_W) { struct sect ndata, nbss; ndata.vaddr = ph[i].p_vaddr; ndata.len = ph[i].p_filesz; nbss.vaddr = ph[i].p_vaddr + ph[i].p_filesz; nbss.len = ph[i].p_memsz - ph[i].p_filesz; if (debug) { fprintf(stderr, " combinining PH %d type %d flags 0x%x with data, ndata = %ld, nbss =%ld\n", i, ph[i].p_type, ph[i].p_flags, ndata.len, nbss.len); } combine(&data, &ndata, 0); combine(&bss, &nbss, 1); } else { struct sect ntxt; ntxt.vaddr = ph[i].p_vaddr; ntxt.len = ph[i].p_filesz; if (debug) { fprintf(stderr, " combinining PH %d type %d flags 0x%x with text, len = %ld\n", i, ph[i].p_type, ph[i].p_flags, ntxt.len); } combine(&text, &ntxt, 0); } /* Remember the lowest segment start address. */ if (ph[i].p_vaddr < cur_vma) cur_vma = ph[i].p_vaddr; } /* Sections must be in order to be converted... */ if (text.vaddr > data.vaddr || data.vaddr > bss.vaddr || text.vaddr + text.len > data.vaddr || data.vaddr + data.len > bss.vaddr) { fprintf(stderr, "Sections ordering prevents a.out conversion.\n"); exit(1); } /* If there's a data section but no text section, then the loader * combined everything into one section. That needs to be the text * section, so just make the data section zero length following text. */ if (data.len && !text.len) { text = data; data.vaddr = text.vaddr + text.len; data.len = 0; } /* If there is a gap between text and data, we'll fill it when we copy * the data, so update the length of the text segment as represented * in a.out to reflect that, since a.out doesn't allow gaps in the * program address space. */ if (text.vaddr + text.len < data.vaddr) text.len = data.vaddr - text.vaddr; /* We now have enough information to cons up an a.out header... */ ep.a.magic = ECOFF_OMAGIC; ep.a.vstamp = 2 * 256 + 10; /* compatible with version 2.10 */ ep.a.tsize = text.len; ep.a.dsize = data.len; ep.a.bsize = bss.len; ep.a.entry = ex.e_entry; ep.a.text_start = text.vaddr; ep.a.data_start = data.vaddr; ep.a.bss_start = bss.vaddr; ep.a.gprmask = 0xf3fffffe; memset(&ep.a.cprmask, 0, sizeof ep.a.cprmask); ep.a.gp_value = 0; /* unused. */ ep.f.f_magic = ECOFF_MAGIC_MIPSEL; ep.f.f_nscns = 6; ep.f.f_timdat = 0; /* bogus */ ep.f.f_symptr = 0; ep.f.f_nsyms = sizeof(struct ecoff_symhdr); ep.f.f_opthdr = sizeof ep.a; ep.f.f_flags = 0x100f; /* Stripped, not sharable. */ memset(esecs, 0, sizeof(esecs)); /* Make ECOFF section headers, with empty stubs for * .rdata/.sdata/.sbss. */ make_ecoff_section_hdrs(&ep, esecs); nsecs = ep.f.f_nscns; /* Make the output file... */ if ((outfile = open(argv[2], O_WRONLY | O_CREAT, 0777)) < 0) { fprintf(stderr, "Unable to create %s: %s\n", argv[2], strerror(errno)); exit(1); } /* Truncate file... */ if (ftruncate(outfile, 0)) { warn("ftruncate %s", argv[2]); } /* Write the headers... */ safewrite(outfile, &ep.f, sizeof(ep.f), "ep.f: write: %s\n"); if (debug) fprintf(stderr, "wrote %d byte file header.\n", sizeof(ep.f)); safewrite(outfile, &ep.a, sizeof(ep.a), "ep.a: write: %s\n"); if (debug) fprintf(stderr, "wrote %d byte a.out header.\n", sizeof(ep.a)); safewrite(outfile, &esecs, sizeof(esecs[0]) * nsecs, "esecs: write: %s\n"); if (debug) fprintf(stderr, "wrote %d bytes of section headers.\n", sizeof(esecs[0]) * nsecs); pad = ((sizeof ep.f + sizeof ep.a + sizeof esecs) & 15); if (pad) { pad = 16 - pad; pad16(outfile, pad, "ipad: write: %s\n"); if (debug) fprintf(stderr, "wrote %d byte pad.\n", pad); } /* Copy the loadable sections. Zero-fill any gaps less than 64k; * complain about any zero-filling, and die if we're asked to * zero-fill more than 64k. */ for (i = 0; i < ex.e_phnum; i++) { /* Unprocessable sections were handled above, so just verify * that the section can be loaded before copying. */ if (ph[i].p_type == Elf_pt_load && ph[i].p_filesz) { if (cur_vma != ph[i].p_vaddr) { unsigned long gap = ph[i].p_vaddr - cur_vma; char obuf[1024]; if (gap > 65536) { fprintf(stderr, "Intersegment gap (%ld bytes) too large.\n", gap); exit(1); } if (debug) fprintf(stderr, "Warning: %ld byte intersegment gap.\n", gap); memset(obuf, 0, sizeof obuf); while (gap) { int count = write(outfile, obuf, (gap > sizeof obuf ? sizeof obuf : gap)); if (count < 0) { fprintf(stderr, "Error writing gap: %s\n", strerror(errno)); exit(1); } gap -= count; } } if (debug) fprintf(stderr, "writing %d bytes...\n", ph[i].p_filesz); copy(outfile, infile, ph[i].p_offset, ph[i].p_filesz); cur_vma = ph[i].p_vaddr + ph[i].p_filesz; } } if (debug) fprintf(stderr, "writing syms at offset 0x%lx\n", (u_long) ep.f.f_symptr + sizeof(symhdr)); /* Copy and translate the symbol table... */ elf_symbol_table_to_ecoff(outfile, infile, &ep, sh[symtabix].sh_offset, sh[symtabix].sh_size, sh[strtabix].sh_offset, sh[strtabix].sh_size); /* * Write a page of padding for boot PROMS that read entire pages. * Without this, they may attempt to read past the end of the * data section, incur an error, and refuse to boot. */ { char obuf[4096]; memset(obuf, 0, sizeof obuf); if (write(outfile, obuf, sizeof(obuf)) != sizeof(obuf)) { fprintf(stderr, "Error writing PROM padding: %s\n", strerror(errno)); exit(1); } } /* Looks like we won... */ exit(0); } void copy(out, in, offset, size) int out, in; off_t offset, size; { char ibuf[4096]; int remaining, cur, count; /* Go the the start of the ELF symbol table... */ if (lseek(in, offset, SEEK_SET) < 0) { perror("copy: lseek"); exit(1); } remaining = size; while (remaining) { cur = remaining; if (cur > sizeof ibuf) cur = sizeof ibuf; remaining -= cur; if ((count = read(in, ibuf, cur)) != cur) { fprintf(stderr, "copy: read: %s\n", count ? strerror(errno) : "premature end of file"); exit(1); } safewrite(out, ibuf, cur, "copy: write: %s\n"); } } /* Combine two segments, which must be contiguous. If pad is true, it's okay for there to be padding between. */ void combine(base, new, pad) struct sect *base, *new; int pad; { if (!base->len) *base = *new; else if (new->len) { if (base->vaddr + base->len != new->vaddr) { if (pad) base->len = new->vaddr - base->vaddr; else { fprintf(stderr, "Non-contiguous data can't be converted.\n"); exit(1); } } base->len += new->len; } } int phcmp(h1, h2) Elf32_Phdr *h1, *h2; { if (h1->p_vaddr > h2->p_vaddr) return 1; else if (h1->p_vaddr < h2->p_vaddr) return -1; else return 0; } char * saveRead(int file, off_t offset, off_t len, char *name) { char *tmp; int count; off_t off; if ((off = lseek(file, offset, SEEK_SET)) < 0) { fprintf(stderr, "%s: fseek: %s\n", name, strerror(errno)); exit(1); } if (!(tmp = (char *) malloc(len))) { fprintf(stderr, "%s: Can't allocate %ld bytes.\n", name, (long) len); exit(1); } count = read(file, tmp, len); if (count != len) { fprintf(stderr, "%s: read: %s.\n", name, count ? strerror(errno) : "End of file reached"); exit(1); } return tmp; } void safewrite(int outfile, void *buf, off_t len, const char *msg) { int written; written = write(outfile, (char *) buf, len); if (written != len) { fprintf(stderr, msg, strerror(errno)); exit(1); } } /* * Output only three ECOFF sections, corresponding to ELF psecs * for text, data, and bss. */ int make_ecoff_section_hdrs(ep, esecs) struct ecoff_exechdr *ep; struct ecoff_scnhdr *esecs; { ep->f.f_nscns = 6; /* XXX */ strcpy(esecs[0].s_name, ".text"); strcpy(esecs[1].s_name, ".data"); strcpy(esecs[2].s_name, ".bss"); esecs[0].s_paddr = esecs[0].s_vaddr = ep->a.text_start; esecs[1].s_paddr = esecs[1].s_vaddr = ep->a.data_start; esecs[2].s_paddr = esecs[2].s_vaddr = ep->a.bss_start; esecs[0].s_size = ep->a.tsize; esecs[1].s_size = ep->a.dsize; esecs[2].s_size = ep->a.bsize; esecs[0].s_scnptr = ECOFF_TXTOFF(ep); esecs[1].s_scnptr = ECOFF_DATOFF(ep); #if 0 esecs[2].s_scnptr = esecs[1].s_scnptr + ECOFF_ROUND(esecs[1].s_size, ECOFF_SEGMENT_ALIGNMENT(ep)); #endif esecs[0].s_relptr = esecs[1].s_relptr = esecs[2].s_relptr = 0; esecs[0].s_lnnoptr = esecs[1].s_lnnoptr = esecs[2].s_lnnoptr = 0; esecs[0].s_nreloc = esecs[1].s_nreloc = esecs[2].s_nreloc = 0; esecs[0].s_nlnno = esecs[1].s_nlnno = esecs[2].s_nlnno = 0; esecs[1].s_flags = 0x100; /* ECOFF rdata */ esecs[3].s_flags = 0x200; /* ECOFF sdata */ esecs[4].s_flags = 0x400; /* ECOFF sbss */ /* * Set the symbol-table offset to point at the end of any * sections we loaded above, so later code can use it to write * symbol table info.. */ ep->f.f_symptr = esecs[1].s_scnptr + esecs[1].s_size; return (ep->f.f_nscns); } /* * Write the ECOFF symbol header. * Guess at how big the symbol table will be. * Mark all symbols as EXTERN (for now). */ void write_ecoff_symhdr(out, ep, symhdrp, nesyms, extsymoff, extstroff, strsize) int out; struct ecoff_exechdr *ep; struct ecoff_symhdr *symhdrp; long nesyms, extsymoff, extstroff, strsize; { if (debug) fprintf(stderr, "writing symhdr for %ld entries at offset 0x%lx\n", nesyms, (u_long) ep->f.f_symptr); ep->f.f_nsyms = sizeof(struct ecoff_symhdr); memset(symhdrp, 0, sizeof(*symhdrp)); symhdrp->esymMax = nesyms; symhdrp->magic = 0x7009;/* XXX */ symhdrp->cbExtOffset = extsymoff; symhdrp->cbSsExtOffset = extstroff; symhdrp->issExtMax = strsize; if (debug) fprintf(stderr, "ECOFF symhdr: symhdr %x, strsize %lx, symsize %lx\n", sizeof(*symhdrp), strsize, (nesyms * sizeof(struct ecoff_extsym))); safewrite(out, symhdrp, sizeof(*symhdrp), "writing symbol header: %s\n"); } void elf_read_syms(elfsymsp, in, symoff, symsize, stroff, strsize) struct elf_syms *elfsymsp; int in; off_t symoff, symsize; off_t stroff, strsize; { register int nsyms; nsyms = symsize / sizeof(Elf32_Sym); /* Suck in the ELF symbol list... */ elfsymsp->elf_syms = (Elf32_Sym *) saveRead(in, symoff, nsyms * sizeof(Elf32_Sym), "ELF symboltable"); elfsymsp->nsymbols = nsyms; /* Suck in the ELF string table... */ elfsymsp->stringtab = (char *) saveRead(in, stroff, strsize, "ELF string table"); elfsymsp->stringsize = strsize; } /* * */ void elf_symbol_table_to_ecoff(out, in, ep, symoff, symsize, stroff, strsize) int out, in; struct ecoff_exechdr *ep; off_t symoff, symsize; off_t stroff, strsize; { struct elf_syms elfsymtab; struct ecoff_syms ecoffsymtab; register u_long ecoff_symhdr_off, symtaboff, stringtaboff; register u_long nextoff, symtabsize, ecoff_strsize; int nsyms; struct ecoff_symhdr symhdr; int padding; /* Read in the ELF symbols. */ elf_read_syms(&elfsymtab, in, symoff, symsize, stroff, strsize); /* Approximate translation to ECOFF. */ translate_syms(&elfsymtab, &ecoffsymtab); nsyms = ecoffsymtab.nsymbols; /* Compute output ECOFF symbol- and string-table offsets. */ ecoff_symhdr_off = ep->f.f_symptr; nextoff = ecoff_symhdr_off + sizeof(struct ecoff_symhdr); stringtaboff = nextoff; ecoff_strsize = ECOFF_ROUND(ecoffsymtab.stringsize, (ECOFF_SEGMENT_ALIGNMENT(ep))); nextoff = stringtaboff + ecoff_strsize; symtaboff = nextoff; symtabsize = nsyms * sizeof(struct ecoff_extsym); symtabsize = ECOFF_ROUND(symtabsize, ECOFF_SEGMENT_ALIGNMENT(ep)); /* Write out the symbol header ... */ write_ecoff_symhdr(out, ep, &symhdr, nsyms, symtaboff, stringtaboff, ecoffsymtab.stringsize); /* Write out the string table... */ padding = ecoff_strsize - ecoffsymtab.stringsize; safewrite(out, ecoffsymtab.stringtab, ecoffsymtab.stringsize, "string table: write: %s\n"); if (padding) pad16(out, padding, "string table: padding: %s\n"); /* Write out the symbol table... */ padding = symtabsize - (nsyms * sizeof(struct ecoff_extsym)); safewrite(out, ecoffsymtab.ecoff_syms, nsyms * sizeof(struct ecoff_extsym), "symbol table: write: %s\n"); if (padding) pad16(out, padding, "symbols: padding: %s\n"); } /* * In-memory translation of ELF symbosl to ECOFF. */ void translate_syms(elfp, ecoffp) struct elf_syms *elfp; struct ecoff_syms *ecoffp; { int i; char *oldstringbase; char *newstrings, *nsp; int nsyms, idx; nsyms = elfp->nsymbols; oldstringbase = elfp->stringtab; /* Allocate space for corresponding ECOFF symbols. */ memset(ecoffp, 0, sizeof(*ecoffp)); ecoffp->nsymbols = 0; ecoffp->ecoff_syms = malloc(sizeof(struct ecoff_extsym) * nsyms); /* we are going to be no bigger than the ELF symbol table. */ ecoffp->stringsize = elfp->stringsize; ecoffp->stringtab = malloc(elfp->stringsize); newstrings = (char *) ecoffp->stringtab; nsp = (char *) ecoffp->stringtab; if (!newstrings) { fprintf(stderr, "No memory for new string table!\n"); exit(1); } /* Copy and translate symbols... */ idx = 0; for (i = 0; i < nsyms; i++) { int binding, type; binding = ELF_SYM_BIND((elfp->elf_syms[i].st_info)); type = ELF_SYM_TYPE((elfp->elf_syms[i].st_info)); /* skip strange symbols */ if (binding == 0) { continue; } /* Copy the symbol into the new table */ strcpy(nsp, oldstringbase + elfp->elf_syms[i].st_name); ecoffp->ecoff_syms[idx].es_strindex = nsp - newstrings; nsp += strlen(nsp) + 1; /* translate symbol types to ECOFF XXX */ ecoffp->ecoff_syms[idx].es_type = 1; ecoffp->ecoff_syms[idx].es_class = 5; /* Symbol values in executables should be compatible. */ ecoffp->ecoff_syms[idx].es_value = elfp->elf_syms[i].st_value; ecoffp->ecoff_syms[idx].es_symauxindex = 0xfffff; idx++; } ecoffp->nsymbols = idx; ecoffp->stringsize = nsp - newstrings; } /* * pad to a 16-byte boundary */ void pad16(int fd, int size, const char *msg) { safewrite(fd, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0", size, msg); } From radwinm@dccinc.com Thu Mar 4 15:43:08 1999 Received: from dcc.dccinc.com ([209.224.159.66]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id PAA19624; Thu, 4 Mar 1999 15:43:06 +0100 (MET) Received-Date: Thu, 4 Mar 1999 15:43:06 +0100 (MET) Received: from DCC-DOM-Message_Server by dcc.dccinc.com with Novell_GroupWise; Thu, 04 Mar 1999 08:49:57 -0500 Message-Id: X-Mailer: Novell GroupWise 5.5 Date: Thu, 04 Mar 1999 08:49:18 -0500 From: "Marshall radwin" To: Subject: Looking for any info on NeTpower Fastseries MP Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Length: 596 Lines: 17 Hey all, I have been "given" a NeTpower Fastseries MP to play with. It has = an R4400 processor in it and (I am told) was originally designed to run = *gasp* NT. Weeeell, I am more interested in running Linux on it! The = person who gave the box to me only had a users guide for it and the = company seems to have gone out of business. Has anyone worked with this = type of box? anyone know where I might get some more technical info on the = box? has anyone gotten the hardhat port of Linux ? TIA Marshall Radwin Systems Analyst Data Communications Corp. radwinm@dccinc.com 317.726.0295 x25 From ryan@end.org Thu Mar 4 15:30:17 1999 Received: from q7.q7.com (ryan@q7.q7.com [206.58.126.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA19098; Thu, 4 Mar 1999 15:30:15 +0100 (MET) Received-Date: Thu, 4 Mar 1999 15:30:15 +0100 (MET) Received: from localhost (ryan@localhost) by q7.q7.com (8.9.1/8.9.1) with SMTP id GAA22695 for ; Thu, 4 Mar 1999 06:30:09 -0800 (PST) Date: Thu, 4 Mar 1999 06:30:09 -0800 (PST) From: Ryan Sweet X-Sender: ryan@q7.q7.com To: linux-mips@fnet.fr Subject: Re: spoofing the kenel header... In-Reply-To: <199903040639.XAA27701@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 564 Lines: 14 Warner, Thanks for your informative message. Do I really need to boot an ecoff image, however? My box is not running CE at the time I load the linux kernel. It starts up with a very simple boot prom that knows just a few things: 1) how to tftpboot if given an image name, an ip, and a server, 2) it wants the image to contain a certain string in the kernel header. On my valid CE images, this string lies somewhere in the first 40 bytes. Would the boot prom also care what executable format the image was in? Ryan Sweet ryan@end.org http://the.end.org/ryan From tor@spacetec.no Thu Mar 4 15:43:59 1999 Received: from pallas.spacetec.no (pallas.spacetec.no [192.51.5.92]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA19649; Thu, 4 Mar 1999 15:43:58 +0100 (MET) Received-Date: Thu, 4 Mar 1999 15:43:58 +0100 (MET) Received: (from tor@localhost) by pallas.spacetec.no (8.9.1a/8.9.1) id PAA05055 for linux-mips@fnet.fr; Thu, 4 Mar 1999 15:43:27 +0100 Message-Id: <199903041443.PAA05055@pallas.spacetec.no> From: tor@spacetec.no (Tor Arntsen) Date: Thu, 4 Mar 1999 15:43:26 +0100 In-Reply-To: Ryan Sweet "Re: spoofing the kenel header..." (Mar 4, 15:36) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: linux-mips@fnet.fr Subject: Re: spoofing the kenel header... Content-Length: 364 Lines: 10 On a side note, would it make sense to maybe let that tftpboot image be a loader that would load the real kernel (also by tftp)? Just in case that first image really *has* to be a coff image (for some reason). Assuming it's easier to build a coff format loader instead of a coff kernel, of course. Or maybe there are too many loaders around already :-) - Tor From imp@harmony.village.org Thu Mar 4 17:46:47 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA21348; Thu, 4 Mar 1999 17:46:46 +0100 (MET) Received-Date: Thu, 4 Mar 1999 17:46:46 +0100 (MET) Received: from rover.village.org (rover.village.org [204.144.255.49]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id RAA19262; Thu, 4 Mar 1999 17:46:43 +0100 (MET) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id QAA37510 for ; Thu, 4 Mar 1999 16:45:20 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA03440 for ; Thu, 4 Mar 1999 09:45:14 -0700 (MST) Message-Id: <199903041645.JAA03440@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: spoofing the kenel header... In-reply-to: Your message of "Thu, 04 Mar 1999 06:30:09 PST." References: Date: Thu, 04 Mar 1999 09:45:14 -0700 From: Warner Losh Content-Length: 1280 Lines: 32 In message Ryan Sweet writes: : Thanks for your informative message. Do I really need to boot an ecoff : image, however? Likely. : My box is not running CE at the time I load the linux : kernel. I know, but it can load the CE kernel, which is almost certainly PECOFF. : It starts up with a very simple boot prom that knows just a few : things: 1) how to tftpboot if given an image name, an ip, and a server, 2) : it wants the image to contain a certain string in the kernel header. On : my valid CE images, this string lies somewhere in the first 40 bytes. : Would the boot prom also care what executable format the image was in? What is the certain string? I think you'll need to create the same kind of image for this. Copy a valid CE image over to your linux machine and run file(1) on it. That should tell you the format of the image. The boot loader has to know something about the image format. Building a coff kernel is very very very easy. Another option that I didn't think about in my last message would be to see if the binutils/gcc still support generating ecoff images. I know at one time a different target would get you this, but haven't looked in a while. I think this is still the case. Warner From imp@harmony.village.org Thu Mar 4 17:46:29 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA21325; Thu, 4 Mar 1999 17:46:27 +0100 (MET) Received-Date: Thu, 4 Mar 1999 17:46:27 +0100 (MET) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id QAA37514 for ; Thu, 4 Mar 1999 16:46:23 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA03452 for ; Thu, 4 Mar 1999 09:46:17 -0700 (MST) Message-Id: <199903041646.JAA03452@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: spoofing the kenel header... In-reply-to: Your message of "Thu, 04 Mar 1999 15:43:26 +0100." <199903041443.PAA05055@pallas.spacetec.no> References: <199903041443.PAA05055@pallas.spacetec.no> Date: Thu, 04 Mar 1999 09:46:17 -0700 From: Warner Losh Content-Length: 546 Lines: 13 In message <199903041443.PAA05055@pallas.spacetec.no> Tor Arntsen writes: : On a side note, would it make sense to maybe let that : tftpboot image be a loader that would load the real : kernel (also by tftp)? Just in case that first image : really *has* to be a coff image (for some reason). : Assuming it's easier to build a coff format loader : instead of a coff kernel, of course. It is easier to build a coff kernel. However, the kernel may need to be tweaked to get the information that the normal loader normally passes to it. Warner From isprite@mail.ru Fri Mar 5 09:17:03 1999 Received: from camel.mail.ru (camel.mail.ru [194.226.198.36]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id JAA28312; Fri, 5 Mar 1999 09:17:02 +0100 (MET) Received-Date: Fri, 5 Mar 1999 09:17:02 +0100 (MET) Received: (from mail@localhost) by camel.mail.ru (8.9.2/8.9.1) id LAA30621 for linux-mips@fnet.fr; Fri, 5 Mar 1999 11:16:54 +0300 (MSK) Date: Fri, 5 Mar 1999 11:16:54 +0300 (MSK) Message-Id: <199903050816.LAA30621@camel.mail.ru> Received: from [193.232.252.55] by koi.mail.ru with HTTP; Fri, 05 Mar 1999 08:16:51 +0000 (GMT) From: "Дмитрий Гареев" To: linux-mips@fnet.fr Subject: Linux Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 1.15 X-Originating-IP: 192.168.5.32 via proxy [193.232.252.55] Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Content-Length: 373 Lines: 9 Hello ! I am found you page, and it is good news for me. Please: I have MIPS server RC3240 (processor R3000), and I haven't Linux for this machine. If you may to help me plees mail me: isprite@mail.ru If you have information about my problem or adresses on what may found this information mail me too. Sorry for my English. :) Sprite. From ralf@lappi.waldorf-gmbh.de Fri Mar 5 23:56:40 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA04367; Fri, 5 Mar 1999 23:56:38 +0100 (MET) Received-Date: Fri, 5 Mar 1999 23:56:38 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-3.uni-koblenz.de [141.26.131.3]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id XAA00464 for ; Fri, 5 Mar 1999 23:56:35 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id VAA06379; Fri, 5 Mar 1999 21:54:38 +0100 Message-ID: <19990305215438.C6370@uni-koblenz.de> Date: Fri, 5 Mar 1999 21:54:38 +0100 From: ralf@uni-koblenz.de To: Warner Losh , linux-mips@fnet.fr Cc: ryan@end.org Subject: Re: spoofing the kenel header... References: <199903040639.XAA27701@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <199903040639.XAA27701@harmony.village.org>; from Warner Losh on Wed, Mar 03, 1999 at 11:39:44PM -0700 Content-Length: 888 Lines: 18 On Wed, Mar 03, 1999 at 11:39:44PM -0700, Warner Losh wrote: > elf2ecoff is short, and I've included it below. As you can see, it is > written for NetBSD, but shouldn't be too hard to port to Linux. I use > the following program all the time to boot OpenBSD kernels (which > don't have a bootstrap loader, so need to be ecoff) all the time. It > does assume that the Elf headers are on your system, which may or may > not be the case for Linux. If it isn't the case, you can grab include > files from ftp.netbsd.org or ftp.openbsd.org. > > Ralf likely has either objcopy working, or a working one of these... I've got elf2ecoff working and independant of me Thomas commited his elf2ecoff variant into the CVS. It is really the only sane way to produce ECOFF from ELF objects since libbfd is way too buggy and incomplete to link ELF into ECOFF under certain circumstances. Ralf From chad@dallas.sgi.com Sat Mar 6 01:55:53 1999 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA06623; Sat, 6 Mar 1999 01:52:09 +0100 (MET) Received-Date: Sat, 6 Mar 1999 01:52:09 +0100 (MET) Received: from relay1.corp.sgi.com ([198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id QAA06947; Fri, 5 Mar 1999 16:35:45 -0800 (PST) mail_from (chad@dallas.sgi.com) Received: from dallas.sgi.com (roctane.dallas.sgi.com [169.238.83.62]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id QAA31718; Fri, 5 Mar 1999 16:35:42 -0800 (PST) Sender: chad@dallas.sgi.com Message-ID: <36E0785D.1758693B@dallas.sgi.com> Date: Fri, 05 Mar 1999 18:35:41 -0600 From: Chad Carlin Reply-To: chad@sgi.com Organization: Silicon Graphics Inc. X-Mailer: Mozilla 4.5C-SGI [en] (X11; I; IRIX64 6.5 IP30) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Bogendoerfer CC: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com, linux-mips@vger.rutgers.edu Subject: Re: 2.2.1 MIPS kernel sources plus Indy kernel binaries uploaded References: <19990227001617.A4022@alpha.franken.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1308 Lines: 40 Thomas, Anyone else have trouble with these on an R4400? I tried a couple times. Both stopped the boot process a the "freeing unused memory" part. Sorry there was no other info. Regards, Chad Thomas Bogendoerfer wrote: > After syncing my two source trees with CVS, I've exported a tarball > and uploaded it to > > ftp://ftp.linux.sgi.com/pub/linux/mips/test/linux-2.2.1-990226.tar.gz > > I've tested compilation for Indy and Olivetti M700 (MIPS Magnum). > > I also uploaded a Indy kernel (map and .config file included): > > ftp://ftp.linux.sgi.com/pub/linux/mips/test/vmlinux-indy-2.2.1-990226.tar.gz > > Thomas. > > -- > This device has completely bogus header. Compaq scores again :-| > It's a host bridge, but it should be called ghost bridge instead ;^) > [Martin `MJ' Mares on linux-kernel] -- ----------------------------------------------------- Chad Carlin Special Systems Silicon Graphics Inc. 972.205.5911 Pager 888.754.1597 VMail 800.414.7994 X5344 chad@sgi.com http://reality.sgi.com/chad ----------------------------------------------------- "flying through hyper space ain't like dusting crops, boy" From K.H.C.vanHouten@research.kpn.com Sat Mar 6 18:51:04 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA12668; Sat, 6 Mar 1999 18:51:03 +0100 (MET) Received-Date: Sat, 6 Mar 1999 18:51:03 +0100 (MET) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J8IQOCDK1G0001I3@research.kpn.com> for linux-mips@fnet.fr; Sat, 6 Mar 1999 18:51:01 +0200 Received: by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id SAA17574; Sat, 06 Mar 1999 18:50:59 +0100 X-URL: http://www-lsdm.research.kpn.com/~karel Date: Sat, 06 Mar 1999 18:50:59 +0100 (MET) From: K.H.C.vanHouten@research.kpn.com (Karel van Houten) Subject: Mounting NetBSD partitions on DECStation Linux To: linux-mips@fnet.fr Cc: K.H.C.vanHouten@research.kpn.com (Houten K.H.C. van ) Message-id: <199903061750.SAA17574@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-Length: 422 Lines: 17 Hi all, I've just patched up genhd.c in order to let it recognize the NetBSD partition table. I have mounted NetBSD and Ultrix partitions on Linux 2.2.1 (read-only, I don't trust the UFS code yet). Can anyone comment on the stability of the UFS code? Can someone confirm that the ufstype of NetBSD is '44bsd', and Ultrix is 'old'? As soon as I've cleaned up my hacks, I'll post a patch. Regards, -- Karel van Houten From engel@math.uni-siegen.de Sat Mar 6 20:27:57 1999 Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.112.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id UAA14194; Sat, 6 Mar 1999 20:27:55 +0100 (MET) Received-Date: Sat, 6 Mar 1999 20:27:55 +0100 (MET) Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id UAA19427 for linux-mips@fnet.fr; Sat, 6 Mar 1999 20:29:12 +0100 (MET) From: Michael Engel Message-Id: <199903061929.UAA19427@fourier.numerik.math.uni-siegen.de> Subject: Re: DECStation 5000/25 To: linux-mips@fnet.fr Date: Sat, 6 Mar 1999 20:29:11 +0100 (MET) In-Reply-To: <199903062120.VAA17755@x-wing.cc.boun.edu.tr> from "Ebutalib Agayev" at Mar 6, 99 09:20:09 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 347 Lines: 12 Hi, > A link on Linux-MIPS page, that points to DECStation 5000/2x information, is > broken. Could you correct it? I've got a DECStation 5000/25 on which I'd like > to run Linux. Yep, some of the information on fnet.fr should definitely be updated ... Take a look at http://decstation.unix-ag.org for more information. regards, Michael Engel From agayev@x-wing.cc.boun.edu.tr Sat Mar 6 20:21:14 1999 Received: from x-wing.cc.boun.edu.tr (x-wing.cc.boun.edu.tr [193.140.199.13]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id UAA13603; Sat, 6 Mar 1999 20:21:11 +0100 (MET) Received-Date: Sat, 6 Mar 1999 20:21:11 +0100 (MET) Received: (from agayev@localhost) by x-wing.cc.boun.edu.tr id VAA17755 for linux-mips@fnet.fr; Sat, 6 Mar 1999 21:20:09 GMT Date: Sat, 6 Mar 1999 21:20:09 GMT From: Ebutalib Agayev Message-Id: <199903062120.VAA17755@x-wing.cc.boun.edu.tr> To: linux-mips@fnet.fr Subject: DECStation 5000/25 Content-Length: 173 Lines: 4 Hi! A link on Linux-MIPS page, that points to DECStation 5000/2x information, is broken. Could you correct it? I've got a DECStation 5000/25 on which I'd like to run Linux. From ralf@lappi.waldorf-gmbh.de Sun Mar 7 00:10:49 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA15996; Sun, 7 Mar 1999 00:10:46 +0100 (MET) Received-Date: Sun, 7 Mar 1999 00:10:46 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-28.uni-koblenz.de [141.26.131.28]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id AAA07896 for ; Sun, 7 Mar 1999 00:10:41 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id AAA13586; Sun, 7 Mar 1999 00:06:42 +0100 Message-ID: <19990307000640.B10228@uni-koblenz.de> Date: Sun, 7 Mar 1999 00:06:40 +0100 From: ralf@uni-koblenz.de To: Chad Carlin , Thomas Bogendoerfer Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com, linux-mips@vger.rutgers.edu Subject: Re: 2.2.1 MIPS kernel sources plus Indy kernel binaries uploaded References: <19990227001617.A4022@alpha.franken.de> <36E0785D.1758693B@dallas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <36E0785D.1758693B@dallas.sgi.com>; from Chad Carlin on Fri, Mar 05, 1999 at 06:35:41PM -0600 Content-Length: 471 Lines: 12 On Fri, Mar 05, 1999 at 06:35:41PM -0600, Chad Carlin wrote: > Anyone else have trouble with these on an R4400? I tried a couple times. Both > stopped the boot process a the "freeing unused memory" part. Sorry there was no It seems one of the ``high priests'' will need get access to one of these machine in order to debug the problem. Did you try the usual hot keys to get a register dump? If that still works, what is the epc value, is the machine looping? Ralf From K.H.C.vanHouten@research.kpn.com Sun Mar 7 17:16:06 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA21721; Sun, 7 Mar 1999 17:16:03 +0100 (MET) Received-Date: Sun, 7 Mar 1999 17:16:03 +0100 (MET) Received: from research.kpn.com (ppp001.research.kpn.com) by research.kpn.com (PMDF V5.1-12 #D3519) with ESMTP id <01J8K1MVX1KI00027Q@research.kpn.com> for linux-mips@fnet.fr; Sun, 7 Mar 1999 17:16:01 +0200 Date: Sun, 07 Mar 1999 17:15:58 +0100 From: Karel van Houten Subject: NetBSD partition support for DECStation Linux Sender: karel@research.kpn.com To: linux-mips@fnet.fr Cc: "Karel van Houten (Kantoor)" Message-id: <36E2A63E.9A535658@research.kpn.com> MIME-version: 1.0 X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.34 i586) Content-type: multipart/mixed; boundary="------------71BF523D022611A84DA1DAD0" Content-Length: 8398 Lines: 268 This is a multi-part message in MIME format. --------------71BF523D022611A84DA1DAD0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I've cleaned up my hacks. The last open issue is about byte-order, my changes work OK on a DECStation, but it might not on other platforms. A few 'b16_to_cpus' might be needed. Anyhow, this is what my kernel prints during boot: ... Partition check: sda: sda1 sda2 (MSDOS partition table) sdb: sdb1 sdb2 sdb3 sdb4 sdb5 (NETBSD partition table, offset 64) sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 sdc8 (ULTRIX partition table) sdd: sdd1 sdd2 sdd3 (SUN partition table) ... Attached is the patch, against Haralds 2.2.1-dec kernel source. Regards, -- Karel van Houten ---------------------------------------------------------- The box said "Requires Windows 95 or better." I can't understand why it won't work on my Linux computer. --------------71BF523D022611A84DA1DAD0 Content-Type: text/plain; charset=us-ascii; name="linux-netbsd.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="linux-netbsd.patch" diff -rubN linux-2.2.1-orig/drivers/block/genhd.c linux-2.2.1-karel/drivers/block/genhd.c --- linux-2.2.1-orig/drivers/block/genhd.c Mon Mar 1 19:44:46 1999 +++ linux-2.2.1-karel/drivers/block/genhd.c Sun Mar 7 14:34:56 1999 @@ -608,7 +608,7 @@ add_partition(hd, current_minor, START_SECT(p), NR_SECTS(p)); } } - printk("\n"); + printk(" (MSDOS partition table)\n"); brelse(bh); return 1; } @@ -681,7 +681,7 @@ partition->p_size); current_minor++; } - printk("\n"); + printk(" (OSF partition table)\n"); brelse(bh); return 1; } @@ -727,8 +727,11 @@ label = (struct sun_disklabel *) bh->b_data; p = label->partitions; if (be16_to_cpu(label->magic) != SUN_LABEL_MAGIC) { + /* + * If it is not a sun disk, keep quiet! printk("Dev %s Sun disklabel: bad magic %04x\n", kdevname(dev), be16_to_cpu(label->magic)); + */ brelse(bh); return 0; } @@ -754,7 +757,7 @@ add_partition(hd, current_minor, st_sector, num_sectors); current_minor++; } - printk("\n"); + printk(" (SUN partition table)\n"); brelse(bh); return 1; } @@ -822,7 +825,7 @@ add_partition(hd, current_minor, p->first_block, p->num_blocks); current_minor++; } - printk("\n"); + printk(" (AMIGA partition table)\n"); brelse(bh); return 1; } @@ -1035,7 +1038,7 @@ ++current_minor; } brelse(bh); - printk("\n"); + printk(" (MAC partition table)\n"); return 1; } @@ -1213,7 +1216,7 @@ add_partition(hd, minor, label->pt_part[i].pi_blkoff, label->pt_part[i].pi_nblocks); - printk("\n"); + printk(" (ULTRIX partition table)\n"); brelse(bh); return 1; } else { @@ -1224,6 +1227,140 @@ #endif /* CONFIG_ULTRIX_PARTITION */ +#ifdef CONFIG_NETBSD_PARTITION +/* + * Native NetBSD disklabels, not inside MSDOS partitions. + * + * Support addded by Karel van Houten + * 1999/03/07 + * + * + */ + +#define LABELOFFSET 64 /* offset of label in sector */ +#define MAXPARTITIONS 8 /* number of partitions */ + +#define DISKMAGIC ((u_int32_t)0x82564557) /* The disk magic number */ + +#define NOFFSETS 4 + +static int label_offset[NOFFSETS] = { 0, 64, 128, 516 }; + +struct netbsd_disklabel { + u_int32_t d_magic; /* the magic number */ + u_int16_t d_type; /* drive type */ + u_int16_t d_subtype; /* controller/d_type specific */ + char d_typename[16]; /* type name, e.g. "eagle" */ + union { + char un_d_packname[16]; /* pack identifier */ + struct { + char *un_d_boot0; /* primary bootstrap name */ + char *un_d_boot1; /* secondary bootstrap name */ + } un_b; + } d_un; +#define d_packname d_un.un_d_packname +#define d_boot0 d_un.un_b.un_d_boot0 +#define d_boot1 d_un.un_b.un_d_boot1 + u_int32_t d_secsize; /* # of bytes per sector */ + u_int32_t d_nsectors; /* # of data sectors per track */ + u_int32_t d_ntracks; /* # of tracks per cylinder */ + u_int32_t d_ncylinders; /* # of data cylinders per unit */ + u_int32_t d_secpercyl; /* # of data sectors per cylinder */ + u_int32_t d_secperunit; /* # of data sectors per unit */ + u_int16_t d_sparespertrack; /* # of spare sectors per track */ + u_int16_t d_sparespercyl; /* # of spare sectors per cylinder */ + u_int32_t d_acylinders; /* # of alt. cylinders per unit */ + u_int16_t d_rpm; /* rotational speed */ + u_int16_t d_interleave; /* hardware sector interleave */ + u_int16_t d_trackskew; /* sector 0 skew, per track */ + u_int16_t d_cylskew; /* sector 0 skew, per cylinder */ + u_int32_t d_headswitch; /* head switch time, usec */ + u_int32_t d_trkseek; /* track-to-track seek, usec */ + u_int32_t d_flags; /* generic flags */ +#define NDDATA 5 + u_int32_t d_drivedata[NDDATA]; /* drive-type specific information */ +#define NSPARE 5 + u_int32_t d_spare[NSPARE]; /* reserved for future use */ + u_int32_t d_magic2; /* the magic number (again) */ + u_int16_t d_checksum; /* xor of data incl. partitions */ + + /* filesystem and partition information: */ + u_int16_t d_npartitions; /* number of partitions in following */ + u_int32_t d_bbsize; /* size of boot area at sn0, bytes */ + u_int32_t d_sbsize; /* max size of fs superblock, bytes */ + struct nbsdpartition { /* the partition table */ + u_int32_t p_size; /* number of sectors in partition */ + u_int32_t p_offset; /* starting sector */ + u_int32_t p_fsize; /* filesystem basic fragment size */ + u_int8_t p_fstype; /* filesystem type, see below */ + u_int8_t p_frag; /* filesystem fragments per block */ + union { + u_int16_t cpg; /* UFS: FS cylinders per group */ + u_int16_t sgs; /* LFS: FS segment shift */ + } __partition_u1; +#define p_cpg __partition_u1.cpg +#define p_sgs __partition_u1.sgs + } d_partitions[MAXPARTITIONS]; /* actually may be more */ +}; + +/* + * Compute checksum for disk label. + */ +static u_int +dkcksum(lp) + register struct netbsd_disklabel *lp; +{ + register u_short *start, *end; + register u_short sum = 0; + + start = (u_short *)lp; + end = (u_short *)&lp->d_partitions[lp->d_npartitions]; + while (start < end) + sum ^= *start++; + return (sum); +} + +static int netbsd_partition(struct gendisk *hd, kdev_t dev, unsigned long first_sector) +{ + int i,j, minor = current_minor; + struct buffer_head *bh; + struct netbsd_disklabel *label; + + + bh = bread (dev, 0, get_ptable_blocksize(dev)); + if (!bh) { + printk (" unable to read block %d\n", 0); + return -1; + } + + for (j=0; jb_data + label_offset[j]); + + if (label->d_magic == DISKMAGIC && label->d_magic2 == DISKMAGIC) { + if (dkcksum(label) != 0) { + printk("Dev %s NetBSD disklabel: bad checksum\n"); + + /* KvH: Should we retry a different offset? */ + brelse(bh); + return 0; + } + for (i=0; i<8; i++, minor++) + if (label->d_partitions[i].p_size) + add_partition(hd, minor, + label->d_partitions[i].p_offset, + label->d_partitions[i].p_size); + printk(" (NETBSD partition table, offset %d)\n", label_offset[j]); + brelse(bh); + return 1; + } + } + brelse(bh); + return 0; +} + +#endif /* CONFIG_NETBSD_PARTITION */ + + static void check_partition(struct gendisk *hd, kdev_t dev) { static int first_time = 1; @@ -1276,6 +1413,10 @@ #ifdef CONFIG_ULTRIX_PARTITION if(ultrix_partition(hd, dev, first_sector)) return; +#endif +#ifdef CONFIG_NETBSD_PARTITION + if(netbsd_partition(hd, dev, first_sector)) + return; #endif printk(" unknown partition table\n"); } diff -rubN linux-2.2.1-orig/fs/Config.in linux-2.2.1-karel/fs/Config.in --- linux-2.2.1-orig/fs/Config.in Mon Mar 1 19:45:35 1999 +++ linux-2.2.1-karel/fs/Config.in Sat Mar 6 16:22:19 1999 @@ -115,6 +115,7 @@ bool 'Solaris (x86) partition table support' CONFIG_SOLARIS_X86_PARTITION if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then bool 'Ultrix partition table support (experimental)' CONFIG_ULTRIX_PARTITION + bool 'NetBSD partition table support (experimental)' CONFIG_NETBSD_PARTITION bool 'Unixware slices support (EXPERIMENTAL)' CONFIG_UNIXWARE_DISKLABEL fi --------------71BF523D022611A84DA1DAD0-- From stealie@intel.cleveland.lug.net Tue Mar 9 04:28:00 1999 Received: from intel.cleveland.lug.net (stealie@intel.cleveland.lug.net [207.166.193.101]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA05055; Tue, 9 Mar 1999 04:27:58 +0100 (MET) Received-Date: Tue, 9 Mar 1999 04:27:58 +0100 (MET) Received: (from stealie@localhost) by intel.cleveland.lug.net (8.8.7/8.8.7) id WAA25391 for linux-mips@fnet.fr; Mon, 8 Mar 1999 22:30:02 -0500 From: Steve Bertoni Message-Id: <199903090330.WAA25391@intel.cleveland.lug.net> To: linux-mips@fnet.fr Date: Mon, 8 Mar 1999 22:30:02 -0500 (EST) Content-Type: text Content-Length: 21 Lines: 1 subscribe linux-mips From ryan@end.org Wed Mar 10 02:02:51 1999 Received: from q7.q7.com (ryan@q7.q7.com [206.58.126.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA12597; Wed, 10 Mar 1999 02:02:50 +0100 (MET) Received-Date: Wed, 10 Mar 1999 02:02:50 +0100 (MET) Received: from localhost (ryan@localhost) by q7.q7.com (8.9.1/8.9.1) with ESMTP id RAA04047 for ; Tue, 9 Mar 1999 17:02:40 -0800 (PST) Date: Tue, 9 Mar 1999 17:02:40 -0800 (PST) From: Ryan Sweet X-Sender: ryan@q7.q7.com To: linux-mips@fnet.fr Subject: Re: Cross-gcc for mipsel-linux In-Reply-To: <19990218102301.F25582@uni-koblenz.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 769 Lines: 23 Is there a canonical source for how to go about building a cross compiler for mipsel-linux? I have tried gcc (it didn't like the -mcpu switch) I've tried the rpms posted on theis list for egcs (they gave me the same error) and I've tried an egcs 1.1.1 (it complains about -pipe not supported. I can't seem to find a single page of instructions that agrees on what versions/patches/processes should be used to build a proper cross-compiler. What's frustrating is that they all seem to work to s apoitn, but none of them will build a kernel. sorry to fill up the list, but I've checked the faq, which points me to the precompiled gcc, which is the one that gives me the -mcpu error. thanks for any help -ryan Ryan Sweet ryan@end.org http://the.end.org/ryan From ryan@end.org Wed Mar 10 02:14:30 1999 Received: from q7.q7.com (ryan@q7.q7.com [206.58.126.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA12677; Wed, 10 Mar 1999 02:14:28 +0100 (MET) Received-Date: Wed, 10 Mar 1999 02:14:28 +0100 (MET) Received: from localhost (ryan@localhost) by q7.q7.com (8.9.1/8.9.1) with ESMTP id RAA04515 for ; Tue, 9 Mar 1999 17:14:25 -0800 (PST) Date: Tue, 9 Mar 1999 17:14:25 -0800 (PST) From: Ryan Sweet X-Sender: ryan@q7.q7.com To: linux-mips@fnet.fr Subject: Re: Cross-gcc for mipsel-linux In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1199 Lines: 43 Forgive me, I just found ralf's updated faq at http://www.lwn.net/1998/0917/linuxmipsfaq.html someone might wish to link to it from the lena.fnet.fr site... I have not quite followd the instructions in the above faq to the letter. I'll pick a clean system and try again. thanks, -ryan On Tue, 9 Mar 1999, Ryan Sweet wrote: > > Is there a canonical source for how to go about building a cross compiler > for mipsel-linux? I have tried gcc (it didn't like the -mcpu switch) I've > tried the rpms posted on theis list for egcs (they gave me the same error) > and I've tried an egcs 1.1.1 (it complains about -pipe not supported. > > I can't seem to find a single page of instructions that agrees on what > versions/patches/processes should be used to build a proper > cross-compiler. What's frustrating is that they all seem to work to s > apoitn, but none of them will build a kernel. > > sorry to fill up the list, but I've checked the faq, which points me to > the precompiled gcc, which is the one that gives me the -mcpu error. > > thanks for any help > > -ryan > > Ryan Sweet > ryan@end.org > http://the.end.org/ryan > > > Ryan Sweet ryan@end.org http://the.end.org/ryan From qiwen@glue.phys.washington.edu Wed Mar 10 03:10:59 1999 Received: from nimbus.esca.com (nimbus.esca.com [192.92.92.27]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id DAA13822; Wed, 10 Mar 1999 03:10:58 +0100 (MET) Received-Date: Wed, 10 Mar 1999 03:10:58 +0100 (MET) Received: from drizzle.esca.com (drizzle.esca.com [199.245.134.254]) by nimbus.esca.com (8.8.7/8.8.7) with SMTP id SAA08584 for ; Tue, 9 Mar 1999 18:10:24 -0800 (PST) Received: from pc537.esca.com by drizzle.esca.com (5.65v4.0/1.1.10.5/25Jan98-0347PM) id AA24744; Tue, 9 Mar 1999 18:10:22 -0800 Message-Id: <36E5D469.CBA42E31@glue.phys.washington.edu> Date: Tue, 09 Mar 1999 18:09:45 -0800 From: Qiwen Lei X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en Mime-Version: 1.0 To: linux-mips@fnet.fr Subject: mip box Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 356 Lines: 7 hi I got a MIPs box, its a dual pro. NEC riscserver 2200, 128MB harddrive. I have some time and want to spend some time hacking the kernel and users code. I am putting linux on my laptop and other machines already. by the way, you will loved this, I was lucky enough to buy five of my last PC WITHOUT microsoft stuff. let me know how I can be of help. From mips@cognito.co.uk Wed Mar 10 11:03:47 1999 Received: from firewall-ii.cognito.co.uk (mail@cognito-gw.cognito.co.uk [195.70.65.253]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA16327; Wed, 10 Mar 1999 11:03:45 +0100 (MET) Received-Date: Wed, 10 Mar 1999 11:03:45 +0100 (MET) Received: (from mail@localhost) by firewall-ii.cognito.co.uk (8.8.7/8.6.10) id LAA25781 for ; Wed, 10 Mar 1999 11:06:10 GMT X-Authentication-Warning: firewall-ii.cognito.co.uk: mail set sender to using -f Received: from sandown(192.9.220.60) by firewall-ii via smap (V1.3) id sma025779; Wed Mar 10 11:06:09 1999 Received: (from mips@localhost) by sandown.cognito.co.uk (8.6.12/8.6.10) id KAA10477; Wed, 10 Mar 1999 10:05:28 GMT Date: Wed, 10 Mar 1999 10:05:28 +0000 (GMT) From: MIPS To: linux-mips@fnet.fr Subject: Problems net booting Decstation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1362 Lines: 37 Hi Can anyone help with the following problems ? I am trying to netboot (bootp/tftp) a Decstation 5000/200. Although I have bootpd running in debug mode on a Linux box, I cannot seem to find any command that will force the Dec to go and collect the IP address and attempt to start a tftp session. (Occasionally I do see bootp requests, but I am not really sure where they're coming from, I've had to guess what the HW address of the Dec is by reading the bootptab from machines that I believe were used to netboot this box before) Although I don't have a real kernel image, I guess that only becomes a problem when it tries to execute it. I have read Paul Antoine/Tom Reiners notes on these issues, but without success. I wonder if anyone can offer any help. If anyone has a simple kernel image and/or RAMDISK image I could use to kickstart this process that would also be very much appreciated. Another thing I am not clear about it loading a RAMDISK image. Should I put this on a floppy, or try to create ext2 partitions on the SCSI disk, or can I use NFS root. I have used NFS root before on 386 arch, I don't know if the code works on the MIPs port. In short any suggestion or help on how to bring up a diskless Linux Decstation would be much appreciated. Many thanks in advance billm@cognito.co.uk Bill Melotti Cognito Limited UK From engel@math.uni-siegen.de Wed Mar 10 11:12:33 1999 Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.112.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA16757; Wed, 10 Mar 1999 11:12:31 +0100 (MET) Received-Date: Wed, 10 Mar 1999 11:12:31 +0100 (MET) Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id LAA28943 for linux-mips@fnet.fr; Wed, 10 Mar 1999 11:13:50 +0100 (MET) From: Michael Engel Message-Id: <199903101013.LAA28943@fourier.numerik.math.uni-siegen.de> Subject: Re: Problems net booting Decstation To: linux-mips@fnet.fr Date: Wed, 10 Mar 1999 11:13:49 +0100 (MET) In-Reply-To: from "MIPS" at Mar 10, 99 10:05:28 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1095 Lines: 29 Hi, > Can anyone help with the following problems ? > > I am trying to netboot (bootp/tftp) a Decstation 5000/200. Although I > have bootpd running in debug mode on a Linux box, I cannot seem to find > any command that will force the Dec to go and collect the IP address and > attempt to start a tftp session. >From the boot monitor, first determine what pseudo TurboChannel slot your system board is with cnfg You should see all your TurboChannel boards listed and an entry for the system board with ethernet address, SCSI devices etc. Let's assume the number is 3 (I really don't know what the value for a 5000/200 is, sorry ...), then you boot via network with boot 3/tftp/vmlinux (replace vmlinux with the name of your kernel image) > (Occasionally I do see bootp requests, but I am not really sure where > they're coming from, I've had to guess what the HW address of the Dec is > by reading the bootptab from machines that I believe were used to netboot > this box before) You can see the hardware address from the cnfg listing ... regards, Michael Engel (engel@unix-ag.org) From mkovach@mkovach.nacs.net Wed Mar 10 12:57:59 1999 Received: from mkovach.nacs.net (mkovach@mkovach.nacs.net [207.166.196.17]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA17317; Wed, 10 Mar 1999 12:57:56 +0100 (MET) Received-Date: Wed, 10 Mar 1999 12:57:56 +0100 (MET) Received: (from mkovach@localhost) by mkovach.nacs.net (8.8.8/8.8.7) id GAA06460 for linux-mips@fnet.fr; Wed, 10 Mar 1999 06:59:39 -0500 Message-ID: <19990310065938.R675@mkovach.nacs.net> Date: Wed, 10 Mar 1999 06:59:38 -0500 From: Mat Kovach To: linux-mips@fnet.fr Subject: Re: Problems net booting Decstation References: <199903101013.LAA28943@fourier.numerik.math.uni-siegen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199903101013.LAA28943@fourier.numerik.math.uni-siegen.de>; from Michael Engel on Wed, Mar 10, 1999 at 11:13:49AM +0100 Content-Length: 1878 Lines: 48 On Wed, Mar 10, 1999 at 11:13:49AM +0100, Michael Engel wrote: : : Hi, : : > Can anyone help with the following problems ? : > : > I am trying to netboot (bootp/tftp) a Decstation 5000/200. Although I : > have bootpd running in debug mode on a Linux box, I cannot seem to find : > any command that will force the Dec to go and collect the IP address and : > attempt to start a tftp session. : You may want to check the revision level of your bootrom to make sure they are no known problems with tftp booting. The NetBSD pages have some info about the bootproms at http://www.netbsd.org/Ports/pmax/board-list.html#proms My Decstation just won't tftp boot, so I tried kernel by booting the kernel using the Ultrix bootloader with some success. Put due to some terrible luck with the eletric company, that drive was corrupted. Anybody know of a place I can pickup some Ultrix install media, cheap? : From the boot monitor, first determine what pseudo TurboChannel slot : your system board is with : cnfg : You should see all your TurboChannel boards listed and an entry for the : system board with ethernet address, SCSI devices etc. Let's assume the : number is 3 (I really don't know what the value for a 5000/200 is, sorry ...), : then you boot via network with : boot 3/tftp/vmlinux : (replace vmlinux with the name of your kernel image) : : > (Occasionally I do see bootp requests, but I am not really sure where : > they're coming from, I've had to guess what the HW address of the Dec is : > by reading the bootptab from machines that I believe were used to netboot : > this box before) : : You can see the hardware address from the cnfg listing ... : : regards, : Michael Engel (engel@unix-ag.org) : -- Mat Kovach mkovach@mkovach.nacs.net This e-mail is brought to you by the letter gamma and number e From jjacocks@helix.nih.gov Wed Mar 10 16:27:07 1999 Received: from helix.nih.gov (helix.nih.gov [128.231.2.3]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA19128; Wed, 10 Mar 1999 16:27:05 +0100 (MET) Received-Date: Wed, 10 Mar 1999 16:27:05 +0100 (MET) Received: (from jjacocks@localhost) by helix.nih.gov (8.9.1a/8.9.1) id KAA04536; Wed, 10 Mar 1999 10:27:02 -0500 (EST) Date: Wed, 10 Mar 1999 10:27:02 -0500 From: "James A. Jacocks" To: linux-mips@fnet.fr Subject: Re: Problems net booting Decstation In-Reply-To: <19990310065938.R675@mkovach.nacs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2120 Lines: 54 Yeah, last time I called DEC, they wanted $800.00 for an Ultrix CD. For a completely unsupported OS! On Wed, 10 Mar 1999, Mat Kovach wrote: > On Wed, Mar 10, 1999 at 11:13:49AM +0100, Michael Engel wrote: > : > : Hi, > : > : > Can anyone help with the following problems ? > : > > : > I am trying to netboot (bootp/tftp) a Decstation 5000/200. Although I > : > have bootpd running in debug mode on a Linux box, I cannot seem to find > : > any command that will force the Dec to go and collect the IP address and > : > attempt to start a tftp session. > : > > You may want to check the revision level of your bootrom to make sure they > are no known problems with tftp booting. The NetBSD pages have some info > about the bootproms at > > http://www.netbsd.org/Ports/pmax/board-list.html#proms > > My Decstation just won't tftp boot, so I tried kernel by booting the kernel > using the Ultrix bootloader with some success. Put due to some terrible > luck with the eletric company, that drive was corrupted. > > Anybody know of a place I can pickup some Ultrix install media, cheap? > > : From the boot monitor, first determine what pseudo TurboChannel slot > : your system board is with > : cnfg > : You should see all your TurboChannel boards listed and an entry for the > : system board with ethernet address, SCSI devices etc. Let's assume the > : number is 3 (I really don't know what the value for a 5000/200 is, sorry ...), > : then you boot via network with > : boot 3/tftp/vmlinux > : (replace vmlinux with the name of your kernel image) > : > : > (Occasionally I do see bootp requests, but I am not really sure where > : > they're coming from, I've had to guess what the HW address of the Dec is > : > by reading the bootptab from machines that I believe were used to netboot > : > this box before) > : > : You can see the hardware address from the cnfg listing ... > : > : regards, > : Michael Engel (engel@unix-ag.org) > : > > -- > Mat Kovach mkovach@mkovach.nacs.net > This e-mail is brought to you by the letter gamma and number e > From chris.holden@gte.net Thu Mar 11 20:38:57 1999 Received: from gte.net (1Cust23.tnt2.oxnard.ca.da.uu.net [208.252.94.23]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id UAA00291; Thu, 11 Mar 1999 20:38:50 +0100 (MET) Received-Date: Thu, 11 Mar 1999 20:38:50 +0100 (MET) Date: Thu, 11 Mar 1999 11:39:33 -0800 From: "Chris Holden" Message-ID: To: linux-mips@fnet.fr Subject: Ooops Typo :) Content-Length: 204 Lines: 7 I happened upon your web site and noticed that the word "definitely" is misspelled (you have it as "definately"). The URL of the page is: http://linux.cis.nctu.edu.tw/MIPS/ I hope this helps. Chris From sebhuet@club-internet.fr Fri Mar 12 08:02:30 1999 Received: from front3.grolier.fr (front3.grolier.fr [194.158.96.53]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id IAA05108; Fri, 12 Mar 1999 08:02:29 +0100 (MET) Received-Date: Fri, 12 Mar 1999 08:02:29 +0100 (MET) Received: from club-internet.fr (ppp-115-124.villette.club-internet.fr [194.158.115.124]) by front3.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id IAA25249 for ; Fri, 12 Mar 1999 08:02:27 +0100 (MET) Sender: seb@front3.grolier.fr Message-ID: <36E8CA0E.89C885C3@club-internet.fr> Date: Fri, 12 Mar 1999 09:02:22 +0100 From: Sebastien HUET Organization: ERE Acoustic X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.3 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: R3000 + Linux Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 188 Lines: 11 Bonjour Je souhaiterai avoir qques info sur l'Иtat du portage linux sur R3000. Je souhaiterai porter LEM sur cette architecture. A++ Seb -- LEM Linux: http://ere-acoustic.fr/lem.html From ralf@lappi.waldorf-gmbh.de Sun Mar 14 01:10:23 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1] (may be forged)) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA19713; Sun, 14 Mar 1999 01:10:21 +0100 (MET) Received-Date: Sun, 14 Mar 1999 01:10:21 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-28.uni-koblenz.de [141.26.131.28]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id BAA04778 for ; Sun, 14 Mar 1999 01:10:16 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id BAA03859; Sun, 14 Mar 1999 01:08:42 +0100 Message-ID: <19990314010841.A3815@uni-koblenz.de> Date: Sun, 14 Mar 1999 01:08:41 +0100 From: ralf@uni-koblenz.de To: linux@engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu Subject: FAQ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 X-Accept-Language: de,en,fr Content-Length: 477 Lines: 13 Hi, I've just put my rewrite of the Linux/MIPS FAQ under CVS control on linus.linux.sgi.com in the module FAQ. I want to invite people to contribute by proofreading, spellchecking and commenting. The FAQ rewrite is using the Linux SGML-Tools package to generate FAQ versions in various data formats. When I find the time I'll arrange that the websites will automatically be updated by the most current version; but somebody else will want to do that? (hint, hint) Ralf From pyoung@prawnsalad.com Sun Mar 14 04:23:30 1999 Received: from winston.irth.net (virgil.1stweb.com [139.144.0.25]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA21127; Sun, 14 Mar 1999 04:23:28 +0100 (MET) Received-Date: Sun, 14 Mar 1999 04:23:28 +0100 (MET) Received: from odysseus ([24.1.141.45]) by winston.irth.net (Netscape Messaging Server 3.6) with SMTP id 558 for ; Sat, 13 Mar 1999 19:20:08 -0800 Message-ID: <000701be6dc8$b5983310$2d8d0118@odysseus> From: "Peter M. Young, Jr." To: Subject: Mips stuff... Date: Sat, 13 Mar 1999 19:13:55 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Content-Length: 265 Lines: 10 Salut! I've recently acquired 2 NEC RISCServers, and I'd like to install Linux on both of them. What state is the port in? What kind of problems am I likely to encounter. I've seen conflicting information about the state of the riscserver port. Thanks, -Peter From lisap@writeme.com Sun Mar 14 09:57:58 1999 Received: from NIH2WAAF (smtp6.site1.csi.com [149.174.183.75]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id JAA23904; Sun, 14 Mar 1999 09:57:57 +0100 (MET) Received-Date: Sun, 14 Mar 1999 09:57:57 +0100 (MET) From: lisap@writeme.com Received: from mail pickup service by csi.com with Microsoft SMTPSVC; Sun, 14 Mar 1999 03:57:18 -0500 Sender: lisap@writeme.com Received: from SMTPmail (cx63917-a.alsv1.occa.home.com [24.1.169.160]) by hil-img-ims-3.compuserve.com (8.8.6/8.8.6/IMS-1.7) with SMTP id DAA29160 for linux-mips@fnet.fr; Sun, 14 Mar 1999 03:57:00 -0500 (EST) Date: Sun, 14 Mar 1999 03:57:00 -0500 (EST) Message-Id: <199903140857.DAA29160@hil-img-ims-3.compuserve.com> Subject: ALLIANCE WANTED Apparently-To: linux-mips@fnet.fr Content-Length: 1474 Lines: 33 begin file :message.txt 1436 bytes Dear Webmaster, I was searching the web and found your web site to be of interest to my clients customers. It looks like you get a lot of web traffic and have many products that are of great demand to your customers. By combining our efforts we may be able to increase web traffic going to both of our web sites. My client site specializes in quality sexual enhancement products. The site is geared toward consumers who want to enhance their sex life. The web site addresses nutritional and psychological aspects of sexuality. My clients site is for adults only and is not pornographic. The site has an online reference guide, free chat site(coming soon), news and information service, free software and links to other sexually interesting resource sites. The sexual products featured on the site are geared toward the consumer who wants to make an informed decision regarding their sexual issues. Each sexual product is backed by scientific research. On line brochures describe sexual issues, products and research studies in easy to understand terms. Featured products may help or enhance sex, sexual intercourse, impotency and pre-ejaculation. Visitors can browse by product name or by health category. If you would like me to contact you regarding a profitable alliance between our two web sites please email me so I may forward your name to my client. Your Health Care Professional, Lisa P lisap@writeme.com From torbjorn.gannholm@fra.se Mon Mar 15 08:18:35 1999 Received: from x.fra.se (x.fra.se [193.12.220.1]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id IAA04091; Mon, 15 Mar 1999 08:18:34 +0100 (MET) Received-Date: Mon, 15 Mar 1999 08:18:34 +0100 (MET) Received: from fra.se by x.fra.se via ESMTP (940816.SGI.8.6.9/940406.SGI.AUTO) id IAA03920; Mon, 15 Mar 1999 08:23:54 +0100 Sender: tobega@fra.se Message-ID: <36ECB588.F39BF967@fra.se> Date: Mon, 15 Mar 1999 08:23:53 +0100 From: Torbjorn Gannholm X-Mailer: Mozilla 4.05 [en] (X11; I; IRIX 5.3 IP12) MIME-Version: 1.0 To: ralf@uni-koblenz.de CC: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu Subject: Re: FAQ References: <19990314010841.A3815@uni-koblenz.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 866 Lines: 27 ralf@uni-koblenz.de wrote: > Hi, > > I've just put my rewrite of the Linux/MIPS FAQ under CVS control on > linus.linux.sgi.com in the module FAQ. I want to invite people to > contribute by proofreading, spellchecking and commenting. > > The FAQ rewrite is using the Linux SGML-Tools package to generate > FAQ versions in various data formats. When I find the time I'll > arrange that the websites will automatically be updated by the > most current version; but somebody else will want to do that? > (hint, hint) > > Ralf There is a proofreading-group collected by the FSF. Mail requests to proofread@gnu.org. You will probably get lots of answers, so you might need to organize the work so as to limit the mail volume. -- /TorbjЖrn This message is a personal message from TorbjЖrn Gannholm and does not necessarily represent the opinion of my employer. From K.H.C.vanHouten@research.kpn.com Mon Mar 15 11:59:49 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA05539; Mon, 15 Mar 1999 11:59:47 +0100 (MET) Received-Date: Mon, 15 Mar 1999 11:59:47 +0100 (MET) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J8UWXFLW7C0001I8@research.kpn.com> for linux-mips@fnet.fr; Mon, 15 Mar 1999 11:59:43 +0200 Received: from sparta.research.kpn.com by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id LAA09756; Mon, 15 Mar 1999 11:59:37 +0100 Date: Mon, 15 Mar 1999 11:59:36 +0100 From: "Houten K.H.C. van (Karel)" Subject: DECStation Linux native partition format ? To: linux-mips@fnet.fr Cc: K.H.C.vanHouten@research.kpn.com Reply-to: K.H.C.vanHouten@research.kpn.com Message-id: <199903151059.LAA09756@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: exmh version 1.6.5 12/11/95 Content-type: text/plain; charset=us-ascii X-Face: ";:TzQQC{mTp~$W,'m4@Lu1Lu$rtG_~5kvYO~F:C'KExk9o1X"iRz[0%{bq?6Aj#>VhSD?v 1W9`.Qsf+P&*iQEL8&y,RDj&U.]!(R-?c-h5h%Iw%r$|%6+Jc>GTJe!_1&A0o'lC[`I#={2BzOXT1P q366I$WL=;[+SDo1RoIT+a}_y68Y:jQ^xp4=*4-ryiymi>hy Content-Length: 877 Lines: 26 Hi fellow DECStation hackers, I was thinking about trying to get a disk bootloader for DECStation Linux. But before we can try to get that running, we have to decide what type of partition table we want to use (the bootloader must fit together with the partition table in the first sectors). The 'native' format for a DECStation is ULTRIX, but that might not be available for all hackers. NetBSD might be an alternative, but we would have to write the fdisk utility for that format. Last of all, we could use the MSDOS/PC format, which works, but is not as flexible as the other ones. What are your opinions? Regards, Karel. -- Karel van Houten ---------------------------------------------------------- The box said "Requires Windows 95 or better." I can't understand why it won't work on my Linux computer. ---------------------------------------------------------- From mkovach@mkovach.nacs.net Mon Mar 15 13:23:55 1999 Received: from mkovach.nacs.net (mkovach@mkovach.nacs.net [207.166.196.17]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA06801; Mon, 15 Mar 1999 13:23:52 +0100 (MET) Received-Date: Mon, 15 Mar 1999 13:23:52 +0100 (MET) Received: (from mkovach@localhost) by mkovach.nacs.net (8.8.8/8.8.7) id HAA16544 for linux-mips@fnet.fr; Mon, 15 Mar 1999 07:25:39 -0500 Message-ID: <19990315072539.Y675@mkovach.nacs.net> Date: Mon, 15 Mar 1999 07:25:39 -0500 From: Mat Kovach To: linux-mips@fnet.fr Subject: Re: DECStation Linux native partition format ? References: <199903151059.LAA09756@sparta.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199903151059.LAA09756@sparta.research.kpn.com>; from Houten K.H.C. van (Karel) on Mon, Mar 15, 1999 at 11:59:36AM +0100 Content-Length: 1117 Lines: 24 On Mon, Mar 15, 1999 at 11:59:36AM +0100, Houten K.H.C. van (Karel) wrote: : : Hi fellow DECStation hackers, : : I was thinking about trying to get a disk bootloader for DECStation Linux. : But before we can try to get that running, we have to decide what type : of partition table we want to use (the bootloader must fit together with : the partition table in the first sectors). : : The 'native' format for a DECStation is ULTRIX, but that might not be : available for all hackers. NetBSD might be an alternative, but we : would have to write the fdisk utility for that format. Last of all, : we could use the MSDOS/PC format, which works, but is not as flexible : as the other ones. : I think a MSDOS/PC format be a good choice for the initial design. While it does not have the flexability, it should have a short development time (?, I have look into booting yet myself). It might not be the final solution, but could be a step towards a final solution. -- Mat Kovach mkovach@mkovach.nacs.net This e-mail is brought to you by the letter gamma and number e From mips@cognito.co.uk Mon Mar 15 14:10:16 1999 Received: from firewall-ii.cognito.co.uk (mail@cognito-gw.cognito.co.uk [195.70.65.253]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA07505; Mon, 15 Mar 1999 14:10:13 +0100 (MET) Received-Date: Mon, 15 Mar 1999 14:10:13 +0100 (MET) Received: (from mail@localhost) by firewall-ii.cognito.co.uk (8.8.7/8.6.10) id OAA05866 for ; Mon, 15 Mar 1999 14:09:17 GMT X-Authentication-Warning: firewall-ii.cognito.co.uk: mail set sender to using -f Received: from sandown(192.9.220.60) by firewall-ii via smap (V1.3) id sma005864; Mon Mar 15 14:09:16 1999 Received: (from mips@localhost) by sandown.cognito.co.uk (8.6.12/8.6.10) id NAA14642; Mon, 15 Mar 1999 13:11:49 GMT Date: Mon, 15 Mar 1999 13:11:49 +0000 (GMT) From: MIPS To: linux-mips@fnet.fr Subject: Porting Linux Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 853 Lines: 22 HI I am considering a port of the MIPs linux to a proprietory MIPs architecture. We already have cross-compilers and boot loaders for this, but these works with 'mips-elf' format. The documents relating to Decstations and so on state you should use 'mips-linux' or 'mipsel-linux' Presumably the format of the 'executable' containing the kernel is only relevant to the bootloader or other startup mechanism ? I guess therefore if we have a mechanism for loading and running mips-elf executables, that would also get a kernel loaded and started, although clearly it will need further work in the ./arch/.... directories. Can anyone comment on that or offer any advice or indicate any pitfalls or perhaps point me towards any linux porting resources. Many thanks in advance for any help. billm@cognito.co.uk Bill Melotti Cognito Limited UK From lembark@wrkhors.com Mon Mar 15 14:22:09 1999 Received: from bird.wrkhors.com (bird.wrkhors.com [206.180.156.161]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA07609; Mon, 15 Mar 1999 14:22:05 +0100 (MET) Received-Date: Mon, 15 Mar 1999 14:22:05 +0100 (MET) Received: from wrkhors.com (poolf8-043.wwa.com [207.241.62.235]) by bird.wrkhors.com (8.8.5/8.8.5) with ESMTP id HAA10234 for ; Mon, 15 Mar 1999 07:20:22 -0600 Sender: lembark@wrkhors.com Message-ID: <36ED0966.81645087@wrkhors.com> Date: Mon, 15 Mar 1999 07:21:42 -0600 From: Steven Lembark Organization: Workhorse Computing X-Mailer: Mozilla 4.07 [en] (X11; U; Linux 2.2.2 i586) MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Re: DECStation Linux native partition format ? References: <199903151059.LAA09756@sparta.research.kpn.com> <19990315072539.Y675@mkovach.nacs.net> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms1583940C1EA5D97B7E2D3DB9" Content-Length: 5925 Lines: 102 This is a cryptographically signed message in MIME format. --------------ms1583940C1EA5D97B7E2D3DB9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > : Hi fellow DECStation hackers, > : > : I was thinking about trying to get a disk bootloader for DECStation Linux. > : But before we can try to get that running, we have to decide what type > : of partition table we want to use (the bootloader must fit together with > : the partition table in the first sectors). > : > : The 'native' format for a DECStation is ULTRIX, but that might not be > : available for all hackers. NetBSD might be an alternative, but we > : would have to write the fdisk utility for that format. Last of all, > : we could use the MSDOS/PC format, which works, but is not as flexible > : as the other ones. > : > > I think a MSDOS/PC format be a good choice for the initial design. While > it does not have the flexability, it should have a short development time > (?, I have look into booting yet myself). It might not be the final solution, > but could be a step towards a final solution. main problem: FAT is slow, error prone and living hell to fix. supporting inodes on FAT file systems is also messy since the allocation chain has noplace to store inode information. this means you have to store the inode in a separate file or in the directory. why not just use the FFS straight out of BSD 4.3? to simplify things restrict the partition to a single cyl. grouip the first time (this will work for boot volumes at least). -- Steven Lembark 2930 W. Palmer St. Workhorse Computing Chicago, IL 60647 lembark@wrkhors.com 800-762-1582 --------------------------------------------------------------------- The opinions expressed here are those of this company. I am the company. --------------------------------------------------------------------- --------------ms1583940C1EA5D97B7E2D3DB9 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIKlwYJKoZIhvcNAQcCoIIKiDCCCoQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC CDIwggT8MIIEZaADAgECAhBLa4QPACg5tIR171/VRyNLMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDEzMDAwMDAw MFoXDTAwMDEzMDIzNTk1OVowggEUMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFzAVBgNVBAMUDlN0ZXZlbiBMZW1iYXJrMSIwIAYJKoZI hvcNAQkBFhNsZW1iYXJrQHdya2hvcnMuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKB gQD5Dh2qHUr6TRD9Fof7Py19Y+C+mbROCqF/4wTc+FOrIpfNDSLrd1dfkQMPzXSgKSKNxFYs bCRNBTHXoyoPuHpgxFeyTg3NFgiVcngC+5aiykX/O9r90C853zzww9+Ka0Xn9NsURBdiL420 ph6vY6JnBLn61i1Gq2nYthiWIeuYuQIDAQABo4IBkjCCAY4wCQYDVR0TBAIwADCBrwYDVR0g BIGnMIAwgAYLYIZIAYb4RQEHAQEwgDAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNp Z24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlT aWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNp Z24AAAAAAAAwEQYJYIZIAYb4QgEBBAQDAgeAMIGGBgpghkgBhvhFAQYDBHgWdmQ0NjUyYmQ2 M2YyMDQ3MDI5Mjk4NzYzYzlkMmYyNzUwNjljNzM1OWJlZDFiMDU5ZGE3NWJjNGJjOTcwMTc0 N2RhNWQzZjIxNDFiZWFkYjJiZDJlODkyMTBhZDZkZjVkMDExNDk5N2ExYjM0NGZkZjNlYTQ1 MGMwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNy bDANBgkqhkiG9w0BAQQFAAOBgQBYZciKn7eXMsgMkYynKSGCa9o/ehR3+hF+d2HhX5RUhN/i O+tcxGyU8+QJtTV6DQsZDxje9b9QCHz0bc5Uid6+tomUCWI0mABjJU4wx0V4zHThfQShoXWg SY1bvaPCkauRZTwkHvcX/Iv2HiLEAA/jz94y+aQUuUE7WK4Jw4DgnTCCAy4wggKXoAMCAQIC EQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYD VQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBD ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5NTla MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg TmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNv cnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqG SIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBo u5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5UiE+H Sr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejARBglg hkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIB Fh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYD VR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bxndPK ZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zDvcjj F7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYICLTCC AikCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2ln biBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkv UlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBD bGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQC EEtrhA8AKDm0hHXvX9VHI0swCQYFKw4DAhoFAKCBojAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw05OTAzMTUxMzIxNDJaMCMGCSqGSIb3DQEJBDEWBBQh3sSW EaV29v2szpEOh42DoguHYzBDBgkqhkiG9w0BCQ8xNjA0MAoGCCqGSIb3DQMHMA4GCCqGSIb3 DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBgkqhkiG9w0BAQEFAASBgAO4NDct 2OMb3M9FkRYdyNasdtXv4nrD1jv/iZ5KAi6V/LaTm40c/WIQIDAsbjzTftpAgmX2cK95d8Eq +qeBYhk+iMkBPW09KSh/734wUC1uLhzAjmj48nvxavRRfuYxomtL809KLUos7bgx+tsRqY7j nxZCi58OGC/nwvfTBwUd --------------ms1583940C1EA5D97B7E2D3DB9-- From glebraiko@netscape.net Mon Mar 15 15:10:52 1999 Received: from www0l.netaddress.usa.net (www0l.netaddress.usa.net [204.68.24.41]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id PAA08790; Mon, 15 Mar 1999 15:10:51 +0100 (MET) Received-Date: Mon, 15 Mar 1999 15:10:51 +0100 (MET) Received: (qmail 1246 invoked by uid 60001); 15 Mar 1999 14:10:42 -0000 Message-ID: <19990315141042.1245.qmail@www0l.netaddress.usa.net> Received: from 204.68.24.41 by www0l via web-mailer(M3.0.0.16) on Mon Mar 15 14:10:42 GMT 1999 Date: 15 Mar 99 15:10:42 MET From: Gleb Raiko To: linux-mips@fnet.fr Subject: Re: Porting Linux X-Mailer: USANET web-mailer (M3.0.0.16) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Length: 1809 Lines: 67 MIPS wrote: > = > HI > = > I am considering a port of the MIPs linux to a proprietory MIPs = > architecture. We already have cross-compilers and boot loaders for this= , = > but these works with 'mips-elf' format. The documents relating to = > Decstations and so on state you should use 'mips-linux' or 'mipsel-linu= x' > = > Presumably the format of the 'executable' containing the kernel is only= = > relevant to the bootloader or other startup mechanism ? I guess therefo= re = > if we have a mechanism for loading and running mips-elf executables, th= at = > would also get a kernel loaded and started, although clearly it will ne= ed = > further work in the ./arch/.... directories. > = > Can anyone comment on that or offer any advice or indicate any = > pitfalls or perhaps point me towards any linux porting resources. > = I strongly recommend use exactly the format the docs say about, until you= don't want to have constant headache about different formats, spurious compiler errors, etc. For example, Linux kernel strongly assumes ELF and = all tryings to build the kernel for ECOFF or a.out will fail. You'll get just= compiler errors on some defines and so on. If your loader recognizes mips-elf only, you may use the following techni= que. 1. Build the kernel as specified. 2. Implement own startup routine which = will set up the kernel sections, program counter, frame pointer, etc. 3. Build= image that contains you startup procedure and the biinary kernel as data.= = You might want to look how DECstation ot Baget/MIMP perform this techniqu= e. Regards, Gleb. = ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at htt= p://home.netscape.com/netcenter/mail From glebraiko@netscape.net Mon Mar 15 17:22:47 1999 Received: from ww185.netaddress.usa.net (ww185.netaddress.usa.net [204.68.24.85]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id RAA10305; Mon, 15 Mar 1999 17:22:45 +0100 (MET) Received-Date: Mon, 15 Mar 1999 17:22:45 +0100 (MET) Received: (qmail 16270 invoked by uid 60001); 15 Mar 1999 16:22:39 -0000 Message-ID: <19990315162239.16269.qmail@ww185.netaddress.usa.net> Received: from 204.68.24.85 by ww185 via web-mailer(M3.0.0.16) on Mon Mar 15 16:22:39 GMT 1999 Date: 15 Mar 99 17:22:39 MET From: Gleb Raiko To: Bill Melotti Subject: Re: Porting Linux CC: linux-mips@fnet.fr X-Mailer: USANET web-mailer (M3.0.0.16) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Length: 1987 Lines: 64 Bill Melotti wrote: > = > Can you indicate perhaps where the kernel assumes ELF ? I grep'd the = > entire 2.0.36 soure for the CONFIG_KERNEL_ELF and could not find a sing= le = > ref (except of course in autoconf.h) Maybe I really just don't = > understand the issue. I will only be compiling the vmlinux 'executable'= =2E = > e.g. Not zImage or any of the others... Sorry, I am too far from sources now. As my memory serves, there are seve= ral defines with asm statements which assume ELF. The simple ways are to try compile the kernel by a.out or ecoff gcc or just to wait until somebody e= lse posts a message. Sorry, again. CONFIG_KERNEL_ELF is obsolete these days. Kernel must be compiled in ELF format. I think, there should be a file in Documentation which describes = that in details. Also, 2.0.36 isn't good choice for MIPS port, I think. You need to pick u= p either 2.1.131 or 2.2.x. = > = > Sorry to bother you if this is trivial, but any guidance appreciated. I= > understand to some level many parts of the kernel e.g. timers, drivers= , > network protocols, but I am very weak on the bits I need to understand = > for a port. If you do not have time for this just say so. The best way, IMO, is just to send a message in the linux-mips mailing li= st, if you have problems with the port. In general, you have to implement own= start up procedure, interrupt and timer handling, and device drivers. Net= work protocols are high level entities and don't need any changes. If you've g= ot problems with a high level code then something goes bad with your port un= til the high level code has bugs or non-portable. The latter case is very rar= e these days. :-) The best way to implement a new driver is to adapt the old one, certainly= =2E Regards, Gleb. ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at htt= p://home.netscape.com/netcenter/mail From tsbogend@alpha.franken.de Mon Mar 15 22:16:44 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA14722; Mon, 15 Mar 1999 22:16:43 +0100 (MET) Received-Date: Mon, 15 Mar 1999 22:16:43 +0100 (MET) Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id WAA10370; Mon, 15 Mar 1999 22:16:41 +0100 (MET) Received: (from tsbogend@localhost) by alpha.franken.de (8.8.7/8.8.5) id VAA02304 for linux-mips@fnet.fr; Mon, 15 Mar 1999 21:22:58 +0100 Message-ID: <19990315212258.A2301@alpha.franken.de> Date: Mon, 15 Mar 1999 21:22:58 +0100 From: Thomas Bogendoerfer To: linux-mips@fnet.fr Subject: Re: Porting Linux References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from MIPS on Mon, Mar 15, 1999 at 01:11:49PM +0000 Content-Length: 653 Lines: 15 On Mon, Mar 15, 1999 at 01:11:49PM +0000, MIPS wrote: > I am considering a port of the MIPs linux to a proprietory MIPs > architecture. We already have cross-compilers and boot loaders for this, > but these works with 'mips-elf' format. The documents relating to > Decstations and so on state you should use 'mips-linux' or 'mipsel-linux' mips-linux is ELF for big endian MIPS, mipsel-linux is ELF for little endian MIPS. Thomas. -- This device has completely bogus header. Compaq scores again :-| It's a host bridge, but it should be called ghost bridge instead ;^) [Martin `MJ' Mares on linux-kernel] From tsbogend@alpha.franken.de Mon Mar 15 22:16:46 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA14728; Mon, 15 Mar 1999 22:16:45 +0100 (MET) Received-Date: Mon, 15 Mar 1999 22:16:45 +0100 (MET) Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id WAA10373; Mon, 15 Mar 1999 22:16:43 +0100 (MET) Received: (from tsbogend@localhost) by alpha.franken.de (8.8.7/8.8.5) id VAA02309 for linux-mips@fnet.fr; Mon, 15 Mar 1999 21:32:19 +0100 Message-ID: <19990315213218.B2301@alpha.franken.de> Date: Mon, 15 Mar 1999 21:32:18 +0100 From: Thomas Bogendoerfer To: linux-mips@fnet.fr Subject: Re: DECStation Linux native partition format ? References: <199903151059.LAA09756@sparta.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <199903151059.LAA09756@sparta.research.kpn.com>; from Houten K.H.C. van (Karel) on Mon, Mar 15, 1999 at 11:59:36AM +0100 Content-Length: 1014 Lines: 22 On Mon, Mar 15, 1999 at 11:59:36AM +0100, Houten K.H.C. van (Karel) wrote: > The 'native' format for a DECStation is ULTRIX, but that might not be > available for all hackers. NetBSD might be an alternative, but we > would have to write the fdisk utility for that format. Last of all, > we could use the MSDOS/PC format, which works, but is not as flexible > as the other ones. If your are able to boot from a FAT filesystem without using any special boot loader, this is one solution. It's available now without any additional work. For people, which don't like FAT filesystem (like me, but I don't have a chance to get rid of the filesystem on my Olivetti M700) you would implement something like SILO (Sparc). It's working similair to LILO but is able to read from ext2 partitions. Thomas. -- This device has completely bogus header. Compaq scores again :-| It's a host bridge, but it should be called ghost bridge instead ;^) [Martin `MJ' Mares on linux-kernel] From paul@milleng.com.au Tue Mar 16 05:46:18 1999 Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id FAA19621; Tue, 16 Mar 1999 05:46:15 +0100 (MET) Received-Date: Tue, 16 Mar 1999 05:46:15 +0100 (MET) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id PAA04036 for ; Tue, 16 Mar 1999 15:46:05 +1100 (EDT) Received: from slither.flatnet.au (CPE-24-192-45-196.nsw.bigpond.net.au [24.192.45.196]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id PAA24709 for ; Tue, 16 Mar 1999 15:46:05 +1100 (EDT) Received: from milleng.com.au (slug.flatnet.au [192.168.1.4]) by slither.flatnet.au (8.8.7/8.8.7) with ESMTP id PAA27463 for ; Tue, 16 Mar 1999 15:48:22 +1100 Message-ID: <36EDE255.719E4A6C@milleng.com.au> Date: Tue, 16 Mar 1999 15:47:17 +1100 From: "Paul M. Antoine" Organization: Millennium Engineering Pty Ltd X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Re: DECStation Linux native partition format ? References: <199903151059.LAA09756@sparta.research.kpn.com> <19990315213218.B2301@alpha.franken.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1582 Lines: 30 Hi gang, On Mon, Mar 15, 1999 at 11:59:36AM +0100, Houten K.H.C. van (Karel) wrote: > The 'native' format for a DECStation is ULTRIX, but that might not be > available for all hackers. NetBSD might be an alternative, but we > would have to write the fdisk utility for that format. Last of all, > we could use the MSDOS/PC format, which works, but is not as flexible > as the other ones. >From the responses so far, it seems most folks have got the wrong end of this particular stick: Karel is asking which *partition* format to use, not which filesystem type to use to boot from. I think the problem here is that the DECstation boot proms only know how to read ULTRIX partition tables, so if we're going to allow folks to boot from the bootprom on power up we're going to have to live with the ULTRIX partition table format. Short of re-writing the boot prom, or writing a multi-stage boot loader (which must be stored on an ULTRIX partition table entry??)... At least that's what I believe to be the case. It could be that the boot proms know how to read a boot loader, which we could replace with a lilo lookalike that understands whatever partition table format we want... but that's not my memory of how the DECstation works. Anyone else?? Regards, Paul ______________________________________________________________________________ Paul M. Antoine Millennium Engineering Pty Ltd email: paul@milleng.com.au Phone: +61 2 9560 7331 large files: pantoine@nsw.bigpond.net.au Fax: +61 2 9560 8708 From K.H.C.vanHouten@research.kpn.com Tue Mar 16 08:37:08 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id IAA20929; Tue, 16 Mar 1999 08:36:57 +0100 (MET) Received-Date: Tue, 16 Mar 1999 08:36:57 +0100 (MET) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J8W45372DS0000AG@research.kpn.com> for linux-mips@fnet.fr; Tue, 16 Mar 1999 08:36:49 +0200 Received: from sparta.research.kpn.com by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id IAA19176; Tue, 16 Mar 1999 08:36:38 +0100 Date: Tue, 16 Mar 1999 08:36:37 +0100 From: "Houten K.H.C. van (Karel)" Subject: Re: DECStation Linux native partition format ? In-reply-to: "Your message of Tue, 16 Mar 1999 15:47:17 +1100." <36EDE255.719E4A6C@milleng.com.au> To: linux-mips@fnet.fr Cc: K.H.C.vanHouten@research.kpn.com Reply-to: K.H.C.vanHouten@research.kpn.com Message-id: <199903160736.IAA19176@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: exmh version 1.6.5 12/11/95 Content-type: text/plain; charset=us-ascii X-Face: ";:TzQQC{mTp~$W,'m4@Lu1Lu$rtG_~5kvYO~F:C'KExk9o1X"iRz[0%{bq?6Aj#>VhSD?v 1W9`.Qsf+P&*iQEL8&y,RDj&U.]!(R-?c-h5h%Iw%r$|%6+Jc>GTJe!_1&A0o'lC[`I#={2BzOXT1P q366I$WL=;[+SDo1RoIT+a}_y68Y:jQ^xp4=*4-ryiymi>hy Content-Length: 2236 Lines: 55 Paul M. Antoine wrote: > Hi gang, > > On Mon, Mar 15, 1999 at 11:59:36AM +0100, Houten K.H.C. van (Karel) wrote: > > The 'native' format for a DECStation is ULTRIX, but that might not be > > available for all hackers. NetBSD might be an alternative, but we > > would have to write the fdisk utility for that format. Last of all, > > we could use the MSDOS/PC format, which works, but is not as flexible > > as the other ones. > > >From the responses so far, it seems most folks have got the wrong end of > this particular stick: Karel is asking which *partition* format to use, > not which filesystem type to use to boot from. > > I think the problem here is that the DECstation boot proms only know how to > read ULTRIX partition tables, so if we're going to allow folks to boot from > the bootprom on power up we're going to have to live with the ULTRIX partition > table format. Short of re-writing the boot prom, or writing a multi-stage > boot loader (which must be stored on an ULTRIX partition table entry??)... > > At least that's what I believe to be the case. It could be that the boot > proms know how to read a boot loader, which we could replace with a lilo > lookalike that understands whatever partition table format we want... but > that's not my memory of how the DECstation works. Anyone else?? Hi Paul, Correct. I was not referring to DOS FAT filesystems, only to the partition table formats. As far as I can tell, the PROM's don't know about ULTRIX partitions, they are only able to read the bootloader from the first disk sectors, and pass the boot command line on to the bootloader. My vote would be to use the NetBSD scheme, because we have a working bootloader for NetBSD in source. Getting this working for linux would involve the following steps: - get the netbsd bootloader to compile under linux - change the bsd ffs code to ext2 code - change fdisk to support netbsd tables. (My kernel already supports NetBSD partition tables) Regards, Karel. -- Karel van Houten ---------------------------------------------------------- The box said "Requires Windows 95 or better." I can't understand why it won't work on my Linux computer. ---------------------------------------------------------- From hkoerfg1@ford.com Tue Mar 16 12:52:56 1999 Received: from mailfw1.ford.com (mailfw1.ford.com [136.1.1.26]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id MAA24256; Tue, 16 Mar 1999 12:52:49 +0100 (MET) Received-Date: Tue, 16 Mar 1999 12:52:49 +0100 (MET) Received: by mailfw1.ford.com id GAA14751 (InterLock SMTP Gateway 3.0 for linux-mips@fnet.fr); Tue, 16 Mar 1999 06:52:37 -0500 Message-Id: <199903161152.GAA14751@mailfw1.ford.com> Received: by mailfw1.ford.com (Internal Mail Agent-1); Tue, 16 Mar 1999 06:52:37 -0500 Date: Tue, 16 Mar 1999 12:52:32 +0100 From: Harald Koerfgen Organization: Ford Motor Company X-Mailer: Mozilla 4.04 [en]C-c32f404p (Win95; I) Mime-Version: 1.0 To: linux-mips@fnet.fr Subject: Re: DECStation Linux native partition format ? References: <199903160736.IAA19176@sparta.research.kpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 4395 Lines: 115 Hello all, I had a quick glance at the topic and I even installed NetBSD on one of my DECstations to make a few experiments. Houten K.H.C. van (Karel) wrote: > > Paul M. Antoine wrote: [snip] > > I think the problem here is that the DECstation boot proms only know how to > > read ULTRIX partition tables, so if we're going to allow folks to boot from > > the bootprom on power up we're going to have to live with the ULTRIX partition > > table format. Short of re-writing the boot prom, or writing a multi-stage > > boot loader (which must be stored on an ULTRIX partition table entry??)... > > > > At least that's what I believe to be the case. It could be that the boot > > proms know how to read a boot loader, which we could replace with a lilo > > lookalike that understands whatever partition table format we want... but > > that's not my memory of how the DECstation works. Anyone else?? [snip] > As far as I can tell, the PROM's don't know about ULTRIX partitions, > they are only able to read the bootloader from the first disk sectors, > and pass the boot command line on to the bootloader. >From what I have been able to find out so far the PROMs load block 0 of the boot device and depending on the information in there continue to load blocks in one of the following manners: 0) load a number of blocks starting from a start block 1) similar to 0 but using a a zero terminated list of (nr_of_blocks, start_block) ranges. This list has to fit into block 0 which limits this list to 61 entries. Or, to be more precise (sprite/dev/devDiskLabel.h): --- start code snippet --- typedef struct Dec_BootMap { int numBlocks; /* Number of blocks to read. */ int startBlock; /* Starting block on disk. */ } Dec_BootMap; /* * Boot block information on the 0th sector. * The boot program is stored in sequences of contiguous blocks. * If mode is 0, there is just one sequence of blocks and one Dec_BootMap * is used. If mode is 1, there are multiple sequences of blocks * and multiple Dec_BootMaps are used, the last with numBlocks = 0. */ typedef struct Dec_DiskBoot { char pad[8]; int magic; /* DEC_BOOT_MAGIC */ int mode; /* Mode for boot info. */ int loadAddr; /* Address to start loading. */ int execAddr; /* Address to start execing. */ Dec_BootMap map[61]; /* Position of boot program. */ } Dec_DiskBoot; #define DEC_BOOT_MAGIC 0x02757a --- end code snippet --- That would give us a lot of freedom to put the bootloader wherever we like, and, most important, is absolutley independant of partitioning schemes and filesystems. > My vote would be to use the NetBSD scheme, because we have a working > bootloader for NetBSD in source. Getting this working for linux would > involve the following steps: > > - get the netbsd bootloader to compile under linux > - change the bsd ffs code to ext2 code > - change fdisk to support netbsd tables. > > (My kernel already supports NetBSD partition tables) > > Regards, > Karel. I guess there are a number of people who want to have Ultrix or *BSD and Linux residing on the same disk, are there? If so, we have to use Ultrix or *BSD partition tables and in either case we have to hack fdisk to support them. Another point is, if booting via multiple sequences of blocks really work, we don't have size restrictions on the bootloader where Ultrix and *BSD are limited to 7.5 KB, probably for historical reasons. Looks like time for some further experiments... Greetings, Harald From ralf@lappi.waldorf-gmbh.de Tue Mar 16 17:08:31 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA25863; Tue, 16 Mar 1999 17:08:27 +0100 (MET) Received-Date: Tue, 16 Mar 1999 17:08:27 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-24.uni-koblenz.de [141.26.131.24]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id RAA08196 for ; Tue, 16 Mar 1999 17:08:14 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id NAA10516; Tue, 16 Mar 1999 13:16:53 +0100 Message-ID: <19990316131653.E9924@uni-koblenz.de> Date: Tue, 16 Mar 1999 13:16:53 +0100 From: ralf@uni-koblenz.de To: Torbjorn Gannholm Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu Subject: Re: FAQ References: <19990314010841.A3815@uni-koblenz.de> <36ECB588.F39BF967@fra.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <36ECB588.F39BF967@fra.se>; from Torbjorn Gannholm on Mon, Mar 15, 1999 at 08:23:53AM +0100 X-Accept-Language: de,en,fr Content-Length: 449 Lines: 11 On Mon, Mar 15, 1999 at 08:23:53AM +0100, Torbjorn Gannholm wrote: > There is a proofreading-group collected by the FSF. Mail requests to > proofread@gnu.org. You will probably get lots of answers, so you might > need to organize the work so as to limit the mail volume. Thanks for the hint; Michael Hill has already sent me a 53kb patch which is going into the CVS asap; I hope somebody else will reread and comment the text once again. Ralf From alhaz@xmission.com Tue Mar 16 17:07:47 1999 Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA25840; Tue, 16 Mar 1999 17:07:45 +0100 (MET) Received-Date: Tue, 16 Mar 1999 17:07:45 +0100 (MET) Received: from xmission.xmission.com ([198.60.22.20] ident=root) by mail.xmission.com with esmtp (Exim 2.05 #3) id 10MwNa-0003Mt-00 for linux-mips@fnet.fr; Tue, 16 Mar 1999 09:07:42 -0700 Received: from alhaz by xmission.xmission.com with local (Exim 2.05 #1) id 10MwNZ-0004Tj-00 for linux-mips@fnet.fr; Tue, 16 Mar 1999 09:07:41 -0700 Subject: Any sort of how-to for Linux on Magnum 4000pc? To: linux-mips@fnet.fr Date: Tue, 16 Mar 1999 09:07:41 -0700 (MST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Eric Jorgensen Content-Length: 890 Lines: 25 I've decided to finally stop putting it off and get this thing set up. So, while I'm still working on getting the 13W3-SVGA adapter figured out and built, I'd kinda like to know what lays before me in a software sort of sense. is there a recommended 2.2.x kernel? 2.1? root filesystem somewhere? Would it be reasonably easy to build the filesystem on an intel linux system and then boot it on the Mips? Granted i can run it in little-endian and big-endian, and that i have irrational dreams about using it to play MP3's, which endian should i use? Also, I may have found that ever elusive hiss-free sound card, but it's a PnP device, and somehow i wonder if isapnptools will function at all on a mips system, any thoughts? (The board appears to be a Terratec Base 1) On the other hand, is support for the Magnum sound card something that appears likely? Thanks much - Eric From ralf@lappi.waldorf-gmbh.de Wed Mar 17 11:24:09 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA12673; Wed, 17 Mar 1999 11:24:03 +0100 (MET) Received-Date: Wed, 17 Mar 1999 11:24:03 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-5.uni-koblenz.de [141.26.131.5]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id LAA03008 for ; Wed, 17 Mar 1999 11:23:44 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id RAA11404; Tue, 16 Mar 1999 17:58:28 +0100 Message-ID: <19990316175827.P9924@uni-koblenz.de> Date: Tue, 16 Mar 1999 17:58:27 +0100 From: ralf@uni-koblenz.de To: Eric Jorgensen , linux-mips@fnet.fr Subject: Re: Any sort of how-to for Linux on Magnum 4000pc? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Eric Jorgensen on Tue, Mar 16, 1999 at 09:07:41AM -0700 X-Accept-Language: de,en,fr Content-Length: 1638 Lines: 40 On Tue, Mar 16, 1999 at 09:07:41AM -0700, Eric Jorgensen wrote: > I've decided to finally stop putting it off and get this thing set > up. So, while I'm still working on getting the 13W3-SVGA adapter figured > out and built, I'd kinda like to know what lays before me in a software > sort of sense. This seems to be a problem which many Linuxers have. Could you produce some ASCII writeup for integration into the HOWTO? Thanks. > is there a recommended 2.2.x kernel? 2.1? root filesystem > somewhere? Would it be reasonably easy to build the filesystem on an intel > linux system and then boot it on the Mips? Get the newest you can get from ftp.linux.sgi.com. > Granted i can run it in little-endian and big-endian, and that i > have irrational dreams about using it to play MP3's, which endian should i > use? The Magnum is currently only supported in little endian mode. Supporting the big endian mode should be a quite easy project as much of the Indy code can be reused. Somebody just needs to do it ... > Also, I may have found that ever elusive hiss-free sound card, but > it's a PnP device, and somehow i wonder if isapnptools will function at > all on a mips system, any thoughts? (The board appears to be a Terratec > Base 1) No idea, I've never taken a look at the ISA PNP tools. At this time all I can say is it's possible to port the ISA PNP tools but no idea about the kind of changes or the size of the effort necessary. > On the other hand, is support for the Magnum sound card something > that appears likely? Yes, because it's a fairly simple device driver - it just needs to be written. Ralf From babydr@baby-dragons.com Tue Mar 16 18:04:54 1999 Received: from filesrv1.baby-dragons.com (babydr@filesrv1.baby-dragons.com [199.33.245.55]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA27105; Tue, 16 Mar 1999 18:04:51 +0100 (MET) Received-Date: Tue, 16 Mar 1999 18:04:51 +0100 (MET) Received: from localhost (babydr@localhost) by filesrv1.baby-dragons.com (8.9.0/8.8.5) with SMTP id JAA14371; Tue, 16 Mar 1999 09:04:38 -0800 Date: Tue, 16 Mar 1999 09:04:37 -0800 (PST) From: "Mr. James W. Laferriere" To: linux-mips@fnet.fr cc: K.H.C.vanHouten@research.kpn.com Subject: Re: DECStation Linux native partition format ? In-Reply-To: <199903160736.IAA19176@sparta.research.kpn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 3116 Lines: 73 Hello Karel & All , Please lets not follow that path . Just take a look at how much hair pulling goes on in getting an SRM(alpha) boot going using a BSD FS there PLEASE lets try to get something along the line of Silo going . This IMO is about the best os-loader I've come accross . All I can do is ask . Tyfyt, JimL On Tue, 16 Mar 1999, Houten K.H.C. van (Karel) wrote: > Paul M. Antoine wrote: > > Hi gang, > > > > On Mon, Mar 15, 1999 at 11:59:36AM +0100, Houten K.H.C. van (Karel) wrote: > > > The 'native' format for a DECStation is ULTRIX, but that might not be > > > available for all hackers. NetBSD might be an alternative, but we > > > would have to write the fdisk utility for that format. Last of all, > > > we could use the MSDOS/PC format, which works, but is not as flexible > > > as the other ones. > > > > >From the responses so far, it seems most folks have got the wrong end of > > this particular stick: Karel is asking which *partition* format to use, > > not which filesystem type to use to boot from. > > > > I think the problem here is that the DECstation boot proms only know how to > > read ULTRIX partition tables, so if we're going to allow folks to boot from > > the bootprom on power up we're going to have to live with the ULTRIX partition > > table format. Short of re-writing the boot prom, or writing a multi-stage > > boot loader (which must be stored on an ULTRIX partition table entry??)... > > > > At least that's what I believe to be the case. It could be that the boot > > proms know how to read a boot loader, which we could replace with a lilo > > lookalike that understands whatever partition table format we want... but > > that's not my memory of how the DECstation works. Anyone else?? > > Hi Paul, > > Correct. I was not referring to DOS FAT filesystems, only to the partition > table formats. > > As far as I can tell, the PROM's don't know about ULTRIX partitions, > they are only able to read the bootloader from the first disk sectors, > and pass the boot command line on to the bootloader. > My vote would be to use the NetBSD scheme, because we have a working > bootloader for NetBSD in source. Getting this working for linux would > involve the following steps: > > - get the netbsd bootloader to compile under linux > - change the bsd ffs code to ext2 code > - change fdisk to support netbsd tables. > > (My kernel already supports NetBSD partition tables) > > Regards, > Karel. > > -- > Karel van Houten > > ---------------------------------------------------------- > The box said "Requires Windows 95 or better." > I can't understand why it won't work on my Linux computer. > ---------------------------------------------------------- > > > , JimL +-----------------------------------------------------------------------+ | James W. Laferriere - Network Engineer - babydr@baby-dragons.com | | System Techniques - 25416 - 22nd S. - Des-Moines, WA 98198 | | Give me VMS -or- Give me Linux -but- only on AXP | +-----------------------------------------------------------------------+ From R.vandenBerg@inter.NL.net Tue Mar 16 18:19:36 1999 Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA27219; Tue, 16 Mar 1999 18:19:35 +0100 (MET) Received-Date: Tue, 16 Mar 1999 18:19:35 +0100 (MET) Received: from dutch.mountain by altrade.nijmegen.inter.nl.net via hn51-28.Hoorn.NL.net [193.79.46.192] with ESMTP id SAA08906 (8.8.8/3.40); Tue, 16 Mar 1999 18:17:46 +0100 (MET) Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain via in.smtpd with smtp id for ; Tue, 16 Mar 1999 18:16:23 +0100 (MET) (Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26) Date: Tue, 16 Mar 1999 18:16:22 +0100 (MET) From: Richard van den Berg X-Sender: ravdberg@whale.dutch.mountain To: ralf@uni-koblenz.de cc: Torbjorn Gannholm , linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu Subject: Re: FAQ In-Reply-To: <19990316131653.E9924@uni-koblenz.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 756 Lines: 20 On Tue, 16 Mar 1999 ralf@uni-koblenz.de wrote: > On Mon, Mar 15, 1999 at 08:23:53AM +0100, Torbjorn Gannholm wrote: > > There is a proofreading-group collected by the FSF. Mail requests to > > proofread@gnu.org. You will probably get lots of answers, so you might > > need to organize the work so as to limit the mail volume. > Thanks for the hint; Michael Hill has already sent me a 53kb patch which > is going into the CVS asap; I hope somebody else will reread and comment > the text once again. An outdated linux-doc-sgml package has prevented me doing so, when updated I'll read it. P.S. is cvs read-only possible at linus.linux.sgi.com? I've tried without succes getting a permission denied. Instead I've ftp'ed the cvs tree. Regards, Richard From David_Wilkins@sonat.com Tue Mar 16 19:58:42 1999 Received: from sntnotes1.sonat.com (sntnotes1.sonat.com [208.246.152.24]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id TAA29225; Tue, 16 Mar 1999 19:58:40 +0100 (MET) Received-Date: Tue, 16 Mar 1999 19:58:40 +0100 (MET) From: David_Wilkins@sonat.com Received: by sntnotes1.sonat.com(Lotus SMTP MTA v4.6.2 (693.3 8-11-1998)) id 86256736.006848A4 ; Tue, 16 Mar 1999 12:59:03 -0600 X-Lotus-FromDomain: SONAT To: linux-mips@fnet.fr Message-ID: <86256736.00684753.00@sntnotes1.sonat.com> Date: Tue, 16 Mar 1999 12:57:34 -0600 Subject: Mips Port - Xterminals? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Content-Length: 540 Lines: 16 I have some old (7) X-Terminals from Tektronix. They appear to be based on the R4xxx chipset. In your estimation, for a reasonably competent C-Programmer, how long to make the MIPS port work on one of these? I have Linux i386 and love it, and would love to teach these X-Terminals how to be real computers. There is no harddrive, but it remote boots via TFTP or NFS. I understand that X-Free86 would be required for X-Windows, etc. I would like to know your opinion before twisting some arms to get the hardware specs. Thanx! dhw From tsbogend@alpha.franken.de Tue Mar 16 23:04:33 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA01057; Tue, 16 Mar 1999 23:04:32 +0100 (MET) Received-Date: Tue, 16 Mar 1999 23:04:32 +0100 (MET) Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id XAA26040; Tue, 16 Mar 1999 23:04:30 +0100 (MET) Received: (from tsbogend@localhost) by alpha.franken.de (8.8.7/8.8.5) id WAA02680 for linux-mips@fnet.fr; Tue, 16 Mar 1999 22:06:25 +0100 Message-ID: <19990316220625.A2627@alpha.franken.de> Date: Tue, 16 Mar 1999 22:06:25 +0100 From: Thomas Bogendoerfer To: linux-mips@fnet.fr Subject: Re: Any sort of how-to for Linux on Magnum 4000pc? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Eric Jorgensen on Tue, Mar 16, 1999 at 09:07:41AM -0700 Content-Length: 1982 Lines: 53 On Tue, Mar 16, 1999 at 09:07:41AM -0700, Eric Jorgensen wrote: > is there a recommended 2.2.x kernel? 2.1? the current 2.2.1 kernel built from CVS should be the best bet. I'll upload a kernel in the next days to ftp.linux.sgi.com. > root filesystem somewhere? there is a root filesystem: ftp://ftp.linux.sgi.com/pub/linux/mips/mipsel/root/declinuxroot-990128.tgz. This should work on the Magnum too. An older root filesystem I've made is ftp://ftp.linux.sgi.com/pub/linux/mips/test/root-le-980323.tar.gz > Would it be reasonably easy to build the filesystem on an intel > linux system and then boot it on the Mips? yes. That's how I started, because there was no SCSI driver at that time. > Granted i can run it in little-endian and big-endian, and that i > have irrational dreams about using it to play MP3's, which endian should i > use? for big endian you are at your own, since I don't have any idea how to use the big extension stuff on my Olivetti M700 (Magnum clone). Everthing I've done on the platform is little endian. And I guess it doesn't matter that much for MP3 anyway. > Also, I may have found that ever elusive hiss-free sound card, but > it's a PnP device, and somehow i wonder if isapnptools will function at > all on a mips system, any thoughts? (The board appears to be a Terratec > Base 1) porting isapnp to Magnums is possible. If isapnp uses /dev/port it should work without major changes, if it does x86 asm to do in/out stuff, it's more work. > On the other hand, is support for the Magnum sound card something > that appears likely? if you do it, yes:-) Right now, sound for the Magnum is really low priority on my much too long todo list. It looks like I'm the only one working on the Magnum stuff. Thomas. -- This device has completely bogus header. Compaq scores again :-| It's a host bridge, but it should be called ghost bridge instead ;^) [Martin `MJ' Mares on linux-kernel] From alhaz@xmission.com Wed Mar 17 00:15:40 1999 Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA02458; Wed, 17 Mar 1999 00:15:38 +0100 (MET) Received-Date: Wed, 17 Mar 1999 00:15:38 +0100 (MET) Received: from xmission.xmission.com ([198.60.22.20] ident=root) by mail.xmission.com with esmtp (Exim 2.12 #1) id 10N33d-0003Mz-00 for linux-mips@fnet.fr; Tue, 16 Mar 1999 16:15:33 -0700 Received: from alhaz by xmission.xmission.com with local (Exim 2.12 #1) id 10N33c-0002VM-00 for linux-mips@fnet.fr; Tue, 16 Mar 1999 16:15:32 -0700 Subject: Re: Any sort of how-to for Linux on Magnum 4000pc? To: linux-mips@fnet.fr Date: Tue, 16 Mar 1999 16:15:32 -0700 (MST) In-Reply-To: <19990316220625.A2627@alpha.franken.de> from "Thomas Bogendoerfer" at Mar 16, 99 10:06:25 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Eric Jorgensen Content-Length: 1850 Lines: 47 > the current 2.2.1 kernel built from CVS should be the best bet. I'll > upload a kernel in the next days to ftp.linux.sgi.com > there is a root filesystem: > > ftp://ftp.linux.sgi.com/pub/linux/mips/mipsel/root/declinuxroot-990128.tgz. > > This should work on the Magnum too. An older root filesystem I've made > is > > ftp://ftp.linux.sgi.com/pub/linux/mips/test/root-le-980323.tar.gz > > > Would it be reasonably easy to build the filesystem on an intel > > linux system and then boot it on the Mips? > > yes. That's how I started, because there was no SCSI driver at that time. What I'm thinking of doing here is mounting the scsi drive on my intel system and then moving it to the mips system when it's ready to go. It sounds like that should be possible from what you're saying. > use the big extension stuff on my Olivetti M700 (Magnum clone). Everthing > I've done on the platform is little endian. And I guess it doesn't matter > that much for MP3 anyway. How involved is the bootloader setup? is the ARC prom on the Mips going to act more or less like the ARC prom on my alpha? > porting isapnp to Magnums is possible. If isapnp uses /dev/port it should > work without major changes, if it does x86 asm to do in/out stuff, it's > more work. I'll download the source and give it a look. > > On the other hand, is support for the Magnum sound card something > > that appears likely? > > if you do it, yes:-) Right now, sound for the Magnum is really low priority > on my much too long todo list. It looks like I'm the only one working on > the Magnum stuff. Once upon a time I met the guy who designed the Magnum sound board. Or atleast chatted with him in email. I believe he works at Evans & Southerland now, or did. Maybe I'll grep my old email . . . Thanks for the info, and, ofcourse, for the port. - Eric From tsbogend@alpha.franken.de Wed Mar 17 00:47:33 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA06371; Wed, 17 Mar 1999 00:47:32 +0100 (MET) Received-Date: Wed, 17 Mar 1999 00:47:32 +0100 (MET) Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id AAA27286; Wed, 17 Mar 1999 00:47:30 +0100 (MET) Received: (from tsbogend@localhost) by alpha.franken.de (8.8.7/8.8.5) id AAA04521 for linux-mips@fnet.fr; Wed, 17 Mar 1999 00:44:09 +0100 Message-ID: <19990317004409.B4512@alpha.franken.de> Date: Wed, 17 Mar 1999 00:44:09 +0100 From: Thomas Bogendoerfer To: linux-mips@fnet.fr Subject: Re: Any sort of how-to for Linux on Magnum 4000pc? References: <19990316220625.A2627@alpha.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Eric Jorgensen on Tue, Mar 16, 1999 at 04:15:32PM -0700 Content-Length: 1523 Lines: 36 On Tue, Mar 16, 1999 at 04:15:32PM -0700, Eric Jorgensen wrote: > > the current 2.2.1 kernel built from CVS should be the best bet. I'll > > upload a kernel in the next days to ftp.linux.sgi.com > > there is a root filesystem: ok, here is the kernel ftp://ftp.linux.sgi.com/pub/linux/mips//test/vmlinux-magnum-2.2.1-990316.gz > What I'm thinking of doing here is mounting the scsi drive on my > intel system and then moving it to the mips system when it's ready to go. > It sounds like that should be possible from what you're saying. yes, that should do. You must setup a small dos partition (mine is 20MB, because I usally have some kernels and the M700 config tools lying on that partition) and a normal ext2fs partition (or several of them, if you like). A swap partition is also a good thing to have. > How involved is the bootloader setup? is the ARC prom on the Mips > going to act more or less like the ARC prom on my alpha? yes, it's similair to the Alpha ARC. I'm booting linux by doing following at the arc prompt: c:vmlinux root=/dev/sda2 If you use the first primary partition for the DOS filesystem (I'm not sure, but it's possible that the DOS partition must be the first one) and the second as your ext2fs root filesystem, it should work for you with the same command. Thomas. -- This device has completely bogus header. Compaq scores again :-| It's a host bridge, but it should be called ghost bridge instead ;^) [Martin `MJ' Mares on linux-kernel] From imp@harmony.village.org Wed Mar 17 06:52:32 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id GAA09874; Wed, 17 Mar 1999 06:52:30 +0100 (MET) Received-Date: Wed, 17 Mar 1999 06:52:30 +0100 (MET) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id FAA81340 for ; Wed, 17 Mar 1999 05:52:26 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA07509 for ; Tue, 16 Mar 1999 22:52:14 -0700 (MST) Message-Id: <199903170552.WAA07509@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: Mips Port - Xterminals? In-reply-to: Your message of "Tue, 16 Mar 1999 12:57:34 CST." <86256736.00684753.00@sntnotes1.sonat.com> References: <86256736.00684753.00@sntnotes1.sonat.com> Date: Tue, 16 Mar 1999 22:52:14 -0700 From: Warner Losh Content-Length: 1525 Lines: 29 In message <86256736.00684753.00@sntnotes1.sonat.com> David_Wilkins@sonat.com writes: : I have some old (7) X-Terminals from Tektronix. They appear to be based on : the R4xxx chipset. In your estimation, for a reasonably competent : C-Programmer, how long to make the MIPS port work on one of these? I have : Linux i386 and love it, and would love to teach these X-Terminals how to be : real computers. There is no harddrive, but it remote boots via TFTP or : NFS. : : I understand that X-Free86 would be required for X-Windows, etc. I would : like to know your opinion before twisting some arms to get the hardware : specs. Given the specs, it wouldn't take more than a few weeks/months of off time hacking to get these things working, with the possible exception of X which may take longer. You are looking at interfacing to the boot loader, figuring out where the hardware is and how to probe for it, writing drivers for any hardware that doesn't have drivers and implementing an X server. Most X terminals don't have too many devices to worry about (a graphics engine, a keyboard, a mouse, sometimes some kind of serial interface, an ethernet interface, RAM, ROM and a CPU and sometimes a bell/sound device), so this shouldn't be that hard, if you have specs. If you don't have specs, then you could do it, but it would take a lot of disassembly and patience to get the job done. Oh, and you might have file format conversion issues too. How fast are the R4xxx chips? What models are they, exactly? Warner From ryan@end.org Wed Mar 17 07:08:22 1999 Received: from q7.q7.com (ryan@q7.q7.com [206.58.126.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id HAA10475; Wed, 17 Mar 1999 07:08:21 +0100 (MET) Received-Date: Wed, 17 Mar 1999 07:08:21 +0100 (MET) Received: from localhost (ryan@localhost) by q7.q7.com (8.9.1/8.9.1) with ESMTP id WAA05494; Tue, 16 Mar 1999 22:08:07 -0800 (PST) Date: Tue, 16 Mar 1999 22:08:07 -0800 (PST) From: Ryan Sweet X-Sender: ryan@q7.q7.com To: Warner Losh cc: linux-mips@fnet.fr Subject: Re: Mips Port - Xterminals? In-Reply-To: <199903170552.WAA07509@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2296 Lines: 50 I work for NCD, which now owns the network display unit of Tek, (the unit that made the aforementioned Xterms...). Let me know what models you are working with and I will see what I can do about getting the hardware docs. I plan to work on linux for our current line of terminals (r4300 processor, based on the old tek terminals) very soon now, but I'm currently absorbed in using my spare time (ie, these are not official NCD projects) to get linux going on our low-end CE terminal, as CE is much less useful than NC Bridge, which runs the Xterms... any help with the former would be spectacular. regards, -ryan On Tue, 16 Mar 1999, Warner Losh wrote: > In message <86256736.00684753.00@sntnotes1.sonat.com> > David_Wilkins@sonat.com writes: > : I have some old (7) X-Terminals from Tektronix. They appear to be based on > : the R4xxx chipset. In your estimation, for a reasonably competent > : C-Programmer, how long to make the MIPS port work on one of these? I have > : Linux i386 and love it, and would love to teach these X-Terminals how to be > : real computers. There is no harddrive, but it remote boots via TFTP or > : NFS. > : > : I understand that X-Free86 would be required for X-Windows, etc. I would > : like to know your opinion before twisting some arms to get the hardware > : specs. > > Given the specs, it wouldn't take more than a few weeks/months of off > time hacking to get these things working, with the possible exception > of X which may take longer. You are looking at interfacing to the > boot loader, figuring out where the hardware is and how to probe for > it, writing drivers for any hardware that doesn't have drivers and > implementing an X server. Most X terminals don't have too many > devices to worry about (a graphics engine, a keyboard, a mouse, > sometimes some kind of serial interface, an ethernet interface, RAM, > ROM and a CPU and sometimes a bell/sound device), so this shouldn't be > that hard, if you have specs. If you don't have specs, then you could > do it, but it would take a lot of disassembly and patience to get the > job done. Oh, and you might have file format conversion issues too. > > How fast are the R4xxx chips? What models are they, exactly? > > Warner > Ryan Sweet ryan@end.org http://the.end.org/ryan From ralf@lappi.waldorf-gmbh.de Wed Mar 17 14:23:01 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA14394; Wed, 17 Mar 1999 14:23:00 +0100 (MET) Received-Date: Wed, 17 Mar 1999 14:23:00 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-30.uni-koblenz.de [141.26.131.30]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id OAA17888 for ; Wed, 17 Mar 1999 14:22:11 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id LAA17524; Wed, 17 Mar 1999 11:42:32 +0100 Message-ID: <19990317114231.A17514@uni-koblenz.de> Date: Wed, 17 Mar 1999 11:42:31 +0100 From: ralf@uni-koblenz.de To: Richard van den Berg Cc: Torbjorn Gannholm , linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu Subject: Re: FAQ References: <19990316131653.E9924@uni-koblenz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Richard van den Berg on Tue, Mar 16, 1999 at 06:16:22PM +0100 X-Accept-Language: de,en,fr Content-Length: 1076 Lines: 28 On Tue, Mar 16, 1999 at 06:16:22PM +0100, Richard van den Berg wrote: > An outdated linux-doc-sgml package has prevented me doing so, when updated > I'll read it. I'm using whatever RedHat 5.2's sgml-tools 1.0.7 but still observe some problems. There is for example a strange problem which prevents me from generating GNU-info version. > P.S. is cvs read-only possible at linus.linux.sgi.com? I've tried without > succes getting a permission denied. Instead I've ftp'ed the cvs tree. Yes, it's possible. From the FAQ: 4.2. Anonymous CVS servers. For those who always want to stay on the bleeding edge and want to avoid having to download patch files or full tarballs we also have an anonymous CVS server. Using CVS you can checkout the Linux/MIPS source tree with the following commands: cvs -d :pserver:cvs@linus.linux.sgi.com:/cvs login (Only needed the first time you use anonymous CVS, the password is "cvs") cvs -d :pserver:cvs@linus.linux.sgi.com:/cvs co where you insert linux, libc, or gdb for . Ralf From glebraiko@netscape.net Wed Mar 17 12:18:32 1999 Received: from ww182.netaddress.usa.net (ww182.netaddress.usa.net [204.68.24.82]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id MAA13347; Wed, 17 Mar 1999 12:18:31 +0100 (MET) Received-Date: Wed, 17 Mar 1999 12:18:31 +0100 (MET) Received: (qmail 22310 invoked by uid 60001); 17 Mar 1999 11:18:28 -0000 Message-ID: <19990317111828.22309.qmail@ww182.netaddress.usa.net> Received: from 204.68.24.82 by ww182 via web-mailer(M3.0.0.20) on Wed Mar 17 11:18:28 GMT 1999 Date: 17 Mar 99 12:18:28 MET From: Gleb Raiko To: linux-mips@fnet.fr Subject: Re: [Re: Any sort of how-to for Linux on Magnum 4000pc?] X-Mailer: USANET web-mailer (M3.0.0.20) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Length: 749 Lines: 25 ralf@uni-koblenz.de wrote: > = > The Magnum is currently only supported in little endian mode. = > Supporting the big endian mode should be a quite easy project as much o= f > the Indy code can be reused. Somebody just needs to do it ... > = I've made first try. It was unsuccessful for very simple reason: to boot = and debug the kernel you need to know addresses of prom procedures like print= f and Co. I even hacked RISC/os image to steal those addresses. Didn't help. :-= (. So, it's not that easy, if you haven't got a lot of docs on your Magnum. Gleb. ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at htt= p://home.netscape.com/netcenter/mail From ralf@lappi.waldorf-gmbh.de Wed Mar 17 16:14:32 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA15405; Wed, 17 Mar 1999 16:14:27 +0100 (MET) Received-Date: Wed, 17 Mar 1999 16:14:27 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-22.uni-koblenz.de [141.26.131.22]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id QAA28439 for ; Wed, 17 Mar 1999 16:14:22 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id QAA18680; Wed, 17 Mar 1999 16:05:14 +0100 Message-ID: <19990317160513.M17268@uni-koblenz.de> Date: Wed, 17 Mar 1999 16:05:13 +0100 From: ralf@uni-koblenz.de To: Eric Jorgensen , linux-mips@fnet.fr Subject: Re: Any sort of how-to for Linux on Magnum 4000pc? References: <19990316220625.A2627@alpha.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Eric Jorgensen on Tue, Mar 16, 1999 at 04:15:32PM -0700 X-Accept-Language: de,en,fr Content-Length: 340 Lines: 9 On Tue, Mar 16, 1999 at 04:15:32PM -0700, Eric Jorgensen wrote: > Once upon a time I met the guy who designed the Magnum sound > board. Or atleast chatted with him in email. I believe he works at Evans & > Southerland now, or did. Maybe I'll grep my old email . . . It's Greg Shippen, I think his email is / was gs@xmisson.com. Ralf From ralf@lappi.waldorf-gmbh.de Wed Mar 17 16:13:41 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA15382; Wed, 17 Mar 1999 16:13:39 +0100 (MET) Received-Date: Wed, 17 Mar 1999 16:13:39 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-22.uni-koblenz.de [141.26.131.22]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id QAA28180 for ; Wed, 17 Mar 1999 16:12:33 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id QAA18685; Wed, 17 Mar 1999 16:09:54 +0100 Message-ID: <19990317160954.N17268@uni-koblenz.de> Date: Wed, 17 Mar 1999 16:09:54 +0100 From: ralf@uni-koblenz.de To: Gleb Raiko , linux-mips@fnet.fr Subject: Re: [Re: Any sort of how-to for Linux on Magnum 4000pc?] References: <19990317111828.22309.qmail@ww182.netaddress.usa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <19990317111828.22309.qmail@ww182.netaddress.usa.net>; from Gleb Raiko on Wed, Mar 17, 1999 at 12:18:28PM +0100 X-Accept-Language: de,en,fr Content-Length: 782 Lines: 15 On Wed, Mar 17, 1999 at 12:18:28PM +0100, Gleb Raiko wrote: > I've made first try. It was unsuccessful for very simple reason: to boot and > debug the kernel you need to know addresses of prom procedures like printf and > Co. I even hacked RISC/os image to steal those addresses. Didn't help. :-(. > So, it's not that easy, if you haven't got a lot of docs on your Magnum. I've made an VME bus system based on the old MIPS PROMs working. It was reaonsably simple, given that I had support from the people who made the VME toaster. I think I know most of what is required to boot such a thing. Aside of that, for an initial version the PROMs can even be ignored even though that would mean loosing the possibilty of getting the PROMs Ethernet address and other settings. Ralf From alhaz@xmission.com Wed Mar 17 17:35:10 1999 Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA17128; Wed, 17 Mar 1999 17:34:54 +0100 (MET) Received-Date: Wed, 17 Mar 1999 17:34:54 +0100 (MET) Received: from xmission.xmission.com ([198.60.22.20] ident=root) by mail.xmission.com with esmtp (Exim 2.12 #1) id 10NI5j-0004rv-00 for linux-mips@fnet.fr; Wed, 17 Mar 1999 08:18:43 -0700 Received: from alhaz by xmission.xmission.com with local (Exim 2.12 #1) id 10NI5i-0004ta-00 for linux-mips@fnet.fr; Wed, 17 Mar 1999 08:18:42 -0700 Subject: Re: Any sort of how-to for Linux on Magnum 4000pc? To: linux-mips@fnet.fr Date: Wed, 17 Mar 1999 08:18:41 -0700 (MST) In-Reply-To: <19990316175827.P9924@uni-koblenz.de> from "ralf@uni-koblenz.de" at Mar 16, 99 05:58:27 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Eric Jorgensen Content-Length: 3201 Lines: 73 > > On Tue, Mar 16, 1999 at 09:07:41AM -0700, Eric Jorgensen wrote: > > > I've decided to finally stop putting it off and get this thing set > > up. So, while I'm still working on getting the 13W3-SVGA adapter figured > > out and built, I'd kinda like to know what lays before me in a software > > sort of sense. > > This seems to be a problem which many Linuxers have. Could you produce > some ASCII writeup for integration into the HOWTO? Thanks. Here's a simple pin assignment. Consider this preliminary, I need to consult the PC hardware faq and figure out the correct pin assignments for the ground connection of each of the color signals, which the author of this faq left out. 4. Q. I want to connect a PC type VGA monitor to the Magnum GFX card. What are the pinouts for the cable? A. Joe Westenhaver on c.s.m writes: pin A1 RED to pin 1 of HD-15. pin A2 GREEN to pin 2 of HD-15. pin A3 BLUE to pin 3 of HD-15. pin 1 no contact. pin 2 no contact. pin 3 no contact. pin 4 Horz sync to pin 13 of HD-15. pin 5 Vert sync to pin 14 of HD-15. pin 6 no contact. pin 7 no contact. pin 8 ground. (pin 10) pin 9 ground. (pin 11) pin 10 no contact. 5. Q. Where can I get a 13W3 connector to make my own cable? A. The connector is manufactured by AMP, but according to them the only stocking dealer for this particular item is Powell Electric at (800) 235-7880. The connector must be assembled from component parts. To the best of my knowledge these are the correct part numbers. For the 13W3: Description AMP PN# Cable mount 13W3 Plug Housing 750021-1 Cable mount 13W3 RecepticleHousing 750021-1 Signal contacts. Male 66506-9 Coax contacts for plug 787578-4 Coax contacts for receptacle 787577-2 Plug shielding hardware kit (Shell?) 750403-1 For the HD 15 Male Description AMP PN# D-Sub housing 748364 Signal contacts. Male 748333-4 Shell. Size #1 745171-1 The signal contacts for the cable mount plug and receptacle are the same as standard d-sub connectors. There are many part numbers depending upon wire gage. The connector is also available from Black Box Corp., Lawrence, PA (412) 746-5500 as part number CBCY36732. The cost is $11.30 and is complete although it does not include a shell. I ordered one of these and I (CAD) can verify that it is the correct part and that the pinouts listed for the 13W3 to HD-15 cable are correct. From florian@void.s.bawue.de Wed Mar 17 22:05:07 1999 Received: from nadia.s.bawue.de (root@nadia.s.bawue.de [193.197.11.52]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA20606; Wed, 17 Mar 1999 22:05:04 +0100 (MET) Received-Date: Wed, 17 Mar 1999 22:05:04 +0100 (MET) Received: from void.s.bawue.de (virtual2.s.bawue.de [193.197.10.2]) by nadia.s.bawue.de (8.9.3/8.9.3) with ESMTP id WAA11186 for ; Wed, 17 Mar 1999 22:04:37 +0100 (CET) Received: from florian by void.s.bawue.de with local (Exim 2.11 #1 (Debian)) id 10NMLK-0000Cn-00; Wed, 17 Mar 1999 20:51:06 +0100 Date: Wed, 17 Mar 1999 20:51:06 +0100 From: Florian Laws To: linux-mips@fnet.fr Subject: Linux on an old Siemens RM400? Message-ID: <19990317205106.A780@void.s.bawue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Content-Length: 911 Lines: 23 I have the possibility to get hold of a rather old SNI RM400 server, but before I say "Yes, I want to have it" and afterwards am alone with a big box of high-tech garbage, I'd like to have some opinions. Is it possible to get Linux up and running on this machine? I know that it may need some hacking and even though I've never messed with the Linux kernel before I'm willing to try, but is it worth the while? What I know about the machine at the moment is this: Its a Siemens/Nixdorf RM400 manufactrued in 1991, MIPS dual processor, it is running an antique Version of SINIX, which is not Y2K compliant, that's the reason why the company that owns the machine is giving it away. Current versions of SINIX do not run on the box. I know that the information I can give you today is hardly useful and I am trying to get some more, what information is important that you can help me? Thanks, Florian Laws From engel@math.uni-siegen.de Wed Mar 17 22:30:11 1999 Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.112.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA21632; Wed, 17 Mar 1999 22:29:55 +0100 (MET) Received-Date: Wed, 17 Mar 1999 22:29:55 +0100 (MET) Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id WAA19571 for linux-mips@fnet.fr; Wed, 17 Mar 1999 22:30:57 +0100 (MET) From: Michael Engel Message-Id: <199903172130.WAA19571@fourier.numerik.math.uni-siegen.de> Subject: Re: Linux on an old Siemens RM400? To: linux-mips@fnet.fr Date: Wed, 17 Mar 1999 22:30:56 +0100 (MET) In-Reply-To: <19990317205106.A780@void.s.bawue.de> from "Florian Laws" at Mar 17, 99 08:51:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1387 Lines: 38 Hi, > > I have the possibility to get hold of a rather old SNI RM400 server, > but before I say "Yes, I want to have it" and afterwards am alone > with a big box of high-tech garbage, I'd like to have some opinions. > Is it possible to get Linux up and running on this machine? Possible yes - done no. There is some support for the RM200C and RM200 (the PCI and VLB/ISA based MIPS workstations from SNI) but not yet for the RM400. > I know that it may need some hacking and even though I've never messed > with the Linux kernel before I'm willing to try, but is it worth the > while? Hmmm, that depends on what you want to do with the machine ;-). > What I know about the machine at the moment is this: > > Its a Siemens/Nixdorf RM400 manufactrued in 1991, > MIPS dual processor, > it is running an antique Version of SINIX, which is not Y2K compliant, > that's the reason why the company that owns the machine is giving it away. > Current versions of SINIX do not run on the box. Hmmm, I doubt that Sinix doesn't support a RM400 machine. It will be expensive to upgrade, though ... > I know that the information I can give you today is hardly useful and > I am trying to get some more, what information is important that you > can help me? Before the machine gets thrown away ... if you don't want the machine, let me know ;-). regards, Michael Engel (engel@unix-ag.org) From adyer@Venus.mcs.net Wed Mar 17 23:30:29 1999 Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA22815; Wed, 17 Mar 1999 23:30:22 +0100 (MET) Received-Date: Wed, 17 Mar 1999 23:30:22 +0100 (MET) Received: from Venus.mcs.net (adyer@Venus.mcs.net [192.160.127.92]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id QAA13015 for ; Wed, 17 Mar 1999 16:30:10 -0600 (CST) Received: from localhost (adyer@localhost) by Venus.mcs.net (8.8.7/8.8.2) with SMTP id QAA69006 for ; Wed, 17 Mar 1999 16:30:10 -0600 (CST) Date: Wed, 17 Mar 1999 16:30:09 -0600 (CST) From: Andrew Dyer To: linux-mips@fnet.fr Subject: Re: Any sort of how-to for Linux on Magnum 4000pc? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1368 Lines: 33 On Wed, 17 Mar 1999, Eric Jorgensen wrote: > Here's a simple pin assignment. Consider this preliminary, I need > to consult the PC hardware faq and figure out the correct pin assignments > for the ground connection of each of the color signals, which the author > of this faq left out. > Typically the returns for red green and blue in a VGA connector are run on the adjacent grounds (pins 5, 6, and 7). > 4. Q. I want to connect a PC type VGA monitor to the Magnum GFX > card. What are the pinouts for the cable? > > A. Joe Westenhaver on c.s.m writes: > > pin A1 RED to pin 1 of HD-15. > pin A2 GREEN to pin 2 of HD-15. > pin A3 BLUE to pin 3 of HD-15. > pin 1 no contact. > pin 2 no contact. > pin 3 no contact. > pin 4 Horz sync to pin 13 of HD-15. > pin 5 Vert sync to pin 14 of HD-15. > pin 6 no contact. > pin 7 no contact. > pin 8 ground. (pin 10) > pin 9 ground. (pin 11) > pin 10 no contact. > Andrew Dyer From sfavre@club-internet.fr Thu Mar 18 00:10:15 1999 Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA23595; Thu, 18 Mar 1999 00:10:14 +0100 (MET) Received-Date: Thu, 18 Mar 1999 00:10:14 +0100 (MET) Received: from club-internet.fr (ppp-166-151.villette.club-internet.fr [195.36.166.151]) by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id AAA04198 for ; Thu, 18 Mar 1999 00:10:01 +0100 (MET) Sender: guest@front7.grolier.fr Message-ID: <36F036E2.D186B42@club-internet.fr> Date: Thu, 18 Mar 1999 00:12:34 +0100 From: Sylvain FAVRE X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.1 i586) X-Accept-Language: fr, en MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Re: Linux on an old Siemens RM400? References: <199903172130.WAA19571@fourier.numerik.math.uni-siegen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1568 Lines: 44 Michael Engel wrote: > Hi, > > > > I have the possibility to get hold of a rather old SNI RM400 server, > > but before I say "Yes, I want to have it" and afterwards am alone > > with a big box of high-tech garbage, I'd like to have some opinions. > > Is it possible to get Linux up and running on this machine? > > Possible yes - done no. There is some support for the RM200C and RM200 > (the PCI and VLB/ISA based MIPS workstations from SNI) but not yet for the > RM400. > > > I know that it may need some hacking and even though I've never messed > > with the Linux kernel before I'm willing to try, but is it worth the > > while? > > Hmmm, that depends on what you want to do with the machine ;-). > > > What I know about the machine at the moment is this: > > > > Its a Siemens/Nixdorf RM400 manufactrued in 1991, > > MIPS dual processor, > > it is running an antique Version of SINIX, which is not Y2K compliant, > > that's the reason why the company that owns the machine is giving it away. > > Current versions of SINIX do not run on the box. > > Hmmm, I doubt that Sinix doesn't support a RM400 machine. It > will be expensive to upgrade, though ... > You can install Reliant Unix 5.43C40 , it's Y2K compliant and it's work on old system > > > I know that the information I can give you today is hardly useful and > > I am trying to get some more, what information is important that you > > can help me? > > Before the machine gets thrown away ... if you don't want the machine, let > me know ;-). > > regards, > Michael Engel (engel@unix-ag.org) From sfavre@club-internet.fr Thu Mar 18 00:12:40 1999 Received: from front6.grolier.fr (front6.grolier.fr [194.158.96.56]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA23620; Thu, 18 Mar 1999 00:12:12 +0100 (MET) Received-Date: Thu, 18 Mar 1999 00:12:12 +0100 (MET) Received: from club-internet.fr (ppp-166-151.villette.club-internet.fr [195.36.166.151]) by front6.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id AAA09079 for ; Thu, 18 Mar 1999 00:12:10 +0100 (MET) Sender: guest@front6.grolier.fr Message-ID: <36F03786.E3DC9E72@club-internet.fr> Date: Thu, 18 Mar 1999 00:15:18 +0100 From: Sylvain FAVRE X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.1 i586) X-Accept-Language: fr, en MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Re: Linux on an old Siemens RM400? References: <19990317205106.A780@void.s.bawue.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 121 Lines: 7 I have two RM400, on is sinix native , the other is winnt. What can I do with these computers ? Regards Sylvain FAVRE From dpmgr-nb@admin.ci.new-bern.nc.us Thu Mar 18 06:36:11 1999 Received: from lucky.coastalnet.com (lucky.coastalnet.com [204.183.40.3]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id GAA28493; Thu, 18 Mar 1999 06:36:10 +0100 (MET) Received-Date: Thu, 18 Mar 1999 06:36:10 +0100 (MET) Received: from admin.ci.new-bern.nc.us (pm-nb15-137.coastalnet.com [204.183.43.137]) by lucky.coastalnet.com (8.9.3/8.9.3) with ESMTP id AAA28035 for ; Thu, 18 Mar 1999 00:36:03 -0500 (EST) Message-ID: <36F09062.EBB354CF@admin.ci.new-bern.nc.us> Date: Thu, 18 Mar 1999 00:34:26 -0500 From: Bob Older X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en,ja MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Prime exl 3033's Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 370 Lines: 7 I have two Prime Exl 3033 boxes which run RISC/OS. We have been using them since 1991 and are replacing them. They have been good machines and I think they can be put to good usu, but, I cannot justify paying lisc and maint fees on them to experiment. Would love to get Linux up on them. Anything I might have that you can use?? I sure don't have source, but, ??? From Toni.Kuure@vtt.fi Thu Mar 18 10:25:16 1999 Received: from elemail.ele.vtt.fi (elemail.ele.vtt.fi [130.188.93.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id KAA01118; Thu, 18 Mar 1999 10:25:14 +0100 (MET) Received-Date: Thu, 18 Mar 1999 10:25:14 +0100 (MET) Received: from ele357 (ele357 [130.188.93.157]) by elemail.ele.vtt.fi (8.9.1a/8.9.1) with SMTP id LAA03695 for ; Thu, 18 Mar 1999 11:28:08 +0200 (EET) Message-Id: <4.1.19990318105654.00a3c860@elemail.ele.vtt.fi> X-Sender: tku@elemail.ele.vtt.fi X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 18 Mar 1999 11:24:23 +0200 To: linux-mips@fnet.fr From: Toni Kuure Subject: Sources+patches Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Length: 224 Lines: 11 Hello all. I'm starting to install linux for P-4032 evaluation board with R4300i processor. Where do I find newest sources and patches for cross-compiler and kernel? I'm running cross-compiler in i586. greetings, Toni From RE-Glaue@wiu.edu Thu Mar 18 18:26:55 1999 Received: from uxa.ecn.bgu.edu (root@uxa.ecn.bgu.edu [143.43.32.11]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA05698; Thu, 18 Mar 1999 18:26:54 +0100 (MET) Received-Date: Thu, 18 Mar 1999 18:26:54 +0100 (MET) Received: from ecom5.ecnet.net (mureg3@ecom5 [143.43.32.25]) by uxa.ecn.bgu.edu (8.8.2/8.8.2) with ESMTP id LAA14264; Thu, 18 Mar 1999 11:25:53 -0600 (CST) Received: from localhost (mureg3@localhost) by ecom5.ecnet.net (8.8.8/8.8.8) with SMTP id LAA28935; Thu, 18 Mar 1999 11:25:47 -0600 (CST) X-Authentication-Warning: ecom5.ecnet.net: mureg3 owned process doing -bs Date: Thu, 18 Mar 1999 11:25:46 -0600 (CST) From: Russell E Glaue X-Sender: mureg3@ecom5 Reply-To: Russell E Glaue To: linux@engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu cc: Martin Schulze , debian-mips@lists.debian.org Subject: Little Endian - Debian/Linux/MIPS Port In-Reply-To: <19990316210931.A10315@finlandia.artis.uni-oldenburg.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 3884 Lines: 82 Okay, to sum up the below conversation, the questions are about the Linux port to the Little Endian or linux-mipsel. More particularly Debain Linux on Little Endian, or in my case of the Deskstation Tyne R4600. Here is the story. The Linux Source code, as I was browsing through it, has code in there particularly noted as for the Deskstation Tyne 4600. I assume that this support is general for little endian. Debian Linux port group is working on a port to Big Endian. I am guessing that everyone who can or is willing to help port Linux to Endian has the big endian. This is of course everyone but me (I have little endian). Generally, people have been asking me about the Little Endian port of the Linux Kernel. Mostly asking what the status is or does it exist. The news as I know it. As soon as the necessary hardware comes in for the two Deskstation Tyne MIPS R4600 Little Endian machines that my place of work owns, I am going to begin the long haul of efforts to try and port Linux to Little Endian (more particularly Deskstation Tyne R4600). Whether or not my efforts will be successful is another story. I have been told that although the code exists in the latest kernel for the Deskstation Tyne, supposedly maintenance of that code has been sitting in the source untouched since version 2.0.2x . I am not a kernel hacker and any efforts of mine in trying to hack the Linux kernel to suport little endian will no doubt be unsuccessfull. No binaries of the Linux Kernel compiled for little endian exist in this world (that I am aware of). Cross compilation development tools will need to be put on a i486 machine to use for cross-compiling the Linux Kernel Source code to run on little endian. In Summary. No Linux Kernel binaries exist for little endian. Whether or not a working kernel for little endian can even be cross-compiled for the little endian is dependant upon the current maintenance status of the Linux kernel source code for linux-mipsel which I do not know. So the only thing that those interested in running Linux on little endian can do is either cross their fingers and hope things work out with my efforts, or help develop a running port of linux on little endian which might include cross-compiling and/or kernel hacking. The latter is encouraged. Also, anyone at all out there who can give me solid information about the current maintenance status of linux-mipsel in the Linux Source code, or what not, is appreciated. -----russ----- On Tue, 16 Mar 1999, Martin Schulze wrote: :|Date: Tue, 16 Mar 1999 21:09:32 +0100 :|From: Martin Schulze :|Reply-To: Martin Schulze :|To: Russell E Glaue , debian-mips@lists.debian.org :|Subject: Re: Debian/Linux/MIPS Port :| :|[I miss some traffic here, is there any progress?] :| :|Ulf Carlsson wrote: :|> > I understand that the Current MIPS code in the Linux 2.2.1 kernel includes :|> > support for the Desksation Tyne, but I would like to know if Debian is :|> > planning on including support for this machine in its destribution. :|> :|> If Debian is going to have support this machine currently depends on you as long :|> as you are the only person who is interested in it doing it. Currently I know no :|> other debian developers who have access to Deskstation machines. There are :|> certainly other persons who are interested in *running* Debian/MIPS little :|> endian. :|> :|> The little endian mips is named mipsel and the big endian version is named just :|> mips. Just so you know. :| :|Does this mean we have to come up with binary-mips and binary-mipsel in :|the near future? :| :|Regards, :| :| Joey :| :|-- :|We all know Linux is great... it does infinite loops in 5 seconds. :| - Linus Torvalds :| :|Please always Cc to me when replying to me on the lists. :| From K.H.C.vanHouten@research.kpn.com Thu Mar 18 18:52:51 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA06709; Thu, 18 Mar 1999 18:52:49 +0100 (MET) Received-Date: Thu, 18 Mar 1999 18:52:49 +0100 (MET) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J8ZI8K0FSA00012C@research.kpn.com> for linux-mips@fnet.fr; Thu, 18 Mar 1999 18:52:45 +0200 Received: by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id SAA25644; Thu, 18 Mar 1999 18:52:38 +0100 X-URL: http://www-lsdm.research.kpn.com/~karel Date: Thu, 18 Mar 1999 18:52:38 +0100 (MET) From: K.H.C.vanHouten@research.kpn.com (Karel van Houten) Subject: Re: Little Endian - Debian/Linux/MIPS Port In-reply-to: To: linux-mips@fnet.fr Cc: linux@engr.sgi.com, linux-mips@vger.rutgers.edu, joey@infodrom.north.de, debian-mips@lists.debian.org, RE-Glaue@wiu.edu Message-id: <199903181752.SAA25644@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-Length: 1333 Lines: 35 Hi Russ, Have a look at the DECStation linux port pages at: http://decstation.unix-ag.org/ or at my personal decstation page at: http://www.xs4all.nl/~vhouten/mipsel/ (more up-to-date). This is a Little Endian port of Linux for R3000 / R4000 DECStations. Russ wrote: > > > In Summary. > No Linux Kernel binaries exist for little endian. Whether or not a > working kernel for little endian can even be cross-compiled for the > little endian is dependant upon the current maintenance status of the > Linux kernel source code for linux-mipsel which I do not know. > So the only thing that those interested in running Linux on little endian > can do is either cross their fingers and hope things work out with my > efforts, or help develop a running port of linux on little endian which > might include cross-compiling and/or kernel hacking. The latter is > encouraged. > Also, anyone at all out there who can give me solid information about the > current maintenance status of linux-mipsel in the Linux Source code, or > what not, is appreciated. > -----russ----- -- Karel van Houten ---------------------------------------------------------- The box said "Requires Windows 95 or better." I can't understand why it won't work on my Linux computer. ---------------------------------------------------------- From <@Cologne.DE:karsten@excalibur.cologne.de> Fri Mar 19 06:22:34 1999 Received: from fileserv2.Cologne.DE (fileserv2.cologne.de [193.29.188.3]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id GAA21293; Fri, 19 Mar 1999 06:22:31 +0100 (MET) Received-Date: Fri, 19 Mar 1999 06:22:31 +0100 (MET) Received: from localhost (1459 bytes) by fileserv2.Cologne.DE via rmail with P:stdio/R:bind/T:smtp (sender: ) (ident using unix) id for ; Fri, 19 Mar 1999 06:22:28 +0100 (CET) (Smail-3.2.0.101 1997-Dec-17 #5 built 1998-Jan-19) Received: (from karsten@localhost) by excalibur.cologne.de (8.8.7/8.8.7) id VAA04877; Thu, 18 Mar 1999 21:33:22 +0100 Message-ID: <19990318213321.B4627@excalibur.cologne.de> Date: Thu, 18 Mar 1999 21:33:21 +0100 From: Karsten Merker To: linux-mips@fnet.fr Cc: Toni Kuure Subject: Re: Sources+patches Mail-Followup-To: linux-mips@fnet.fr, Toni Kuure References: <4.1.19990318105654.00a3c860@elemail.ele.vtt.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <4.1.19990318105654.00a3c860@elemail.ele.vtt.fi>; from Toni Kuure on Thu, Mar 18, 1999 at 11:24:23AM +0200 X-No-Archive: yes Content-Length: 612 Lines: 19 Toni Kuure wrote: > I'm starting to install linux for P-4032 evaluation board with R4300i > processor. > > Where do I find newest sources and patches for cross-compiler and kernel? I'm > running cross-compiler in i586. If you have a glibc-based system, you can get RPMs with cross-binutils und cross-compiler from ftp://bolug.uni-bonn.de/mips/. Kernel-Sources are at ftp.linux.sgi.com. HTH, Karsten -- #include Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder Meinungsforschung. From florian@void.s.bawue.de Thu Mar 18 21:53:15 1999 Received: from nadia.s.bawue.de (root@nadia.s.bawue.de [193.197.11.52]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA09754; Thu, 18 Mar 1999 21:53:12 +0100 (MET) Received-Date: Thu, 18 Mar 1999 21:53:12 +0100 (MET) Received: from void.s.bawue.de (virtual11.s.bawue.de [193.197.10.11]) by nadia.s.bawue.de (8.9.3/8.9.3) with ESMTP id VAA03876 for ; Thu, 18 Mar 1999 21:52:44 +0100 (CET) Received: from florian by void.s.bawue.de with local (Exim 2.11 #1 (Debian)) id 10NjcT-0000HL-00; Thu, 18 Mar 1999 21:42:21 +0100 Date: Thu, 18 Mar 1999 21:42:21 +0100 From: Florian Laws To: linux-mips@fnet.fr Subject: Re: Linux on an old Siemens RM400? Message-ID: <19990318214221.A1065@void.s.bawue.de> Mail-Followup-To: linux-mips@fnet.fr References: <199903172130.WAA19571@fourier.numerik.math.uni-siegen.de> <36F036E2.D186B42@club-internet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <36F036E2.D186B42@club-internet.fr>; from Sylvain FAVRE on Thu, Mar 18, 1999 at 12:12:34AM +0100 Content-Length: 951 Lines: 28 On Thu, Mar 18, 1999 at 12:12:34AM +0100, Sylvain FAVRE wrote: > Michael Engel wrote: > > > Hmmm, I doubt that Sinix doesn't support a RM400 machine. It > > will be expensive to upgrade, though ... > > > > You can install Reliant Unix 5.43C40 , it's Y2K compliant and it's work on old > system > Are you sure? The vendor of the company I can get the machine from told them there was no way to make that particular box Y2K compliant. Of course vendors want to sell new hardware too. ;-) But how much does Reliant Unix cost? I dont't think I have the money for this system, and even if I had, I don't think I'd want to spend it on the old box. After all, the machine is 8 years old, and I'd bet my PC ist faster. This is for hack value only. (Although that doesn't mean I really wanted to port Linux to the machine, sorry folks - NetBSD comes to mind. Any opinions?) Thanks, Florian -- I am a signature-virus. Why don't copy me into your sig? From <@Cologne.DE:karsten@excalibur.cologne.de> Fri Mar 19 06:22:46 1999 Received: from fileserv2.Cologne.DE (fileserv2.cologne.de [193.29.188.3]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id GAA21315; Fri, 19 Mar 1999 06:22:40 +0100 (MET) Received-Date: Fri, 19 Mar 1999 06:22:40 +0100 (MET) Received: from localhost (1671 bytes) by fileserv2.Cologne.DE via rmail with P:stdio/R:bind/T:smtp (sender: ) (ident using unix) id for ; Fri, 19 Mar 1999 06:22:28 +0100 (CET) (Smail-3.2.0.101 1997-Dec-17 #5 built 1998-Jan-19) Received: (from karsten@localhost) by excalibur.cologne.de (8.8.7/8.8.7) id VAA05325; Thu, 18 Mar 1999 21:47:39 +0100 Message-ID: <19990318214739.C4627@excalibur.cologne.de> Date: Thu, 18 Mar 1999 21:47:39 +0100 From: Karsten Merker To: linux-mips@fnet.fr, debian-mips Subject: Re: Little Endian - Debian/Linux/MIPS Port Mail-Followup-To: linux-mips@fnet.fr, debian-mips References: <19990316210931.A10315@finlandia.artis.uni-oldenburg.de> <19990318205205.A1101@bun.falkenberg.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <19990318205205.A1101@bun.falkenberg.se>; from Ulf Carlsson on Thu, Mar 18, 1999 at 08:52:05PM -0500 X-No-Archive: yes Content-Length: 676 Lines: 17 On Thu, Mar 18, 1999 at 08:52:05PM -0500, Ulf Carlsson wrote: > On Thu, Mar 18, 1999 at 11:25:46AM -0600, Russell E Glaue wrote: [Questions about the state of little-endian Linux-MIPS] > I think there are RPM binaries of cross compilation tools as well somewhere. ftp://bolug.uni-bonn.de/mips/ (The rpms are for glibc, the src.rpms should also compile on a libc5 system, although I could not test that due to the lack of a libc5-based machine.) Greetings, Karsten -- #include Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder Meinungsforschung. From florian@void.s.bawue.de Thu Mar 18 21:52:51 1999 Received: from nadia.s.bawue.de (root@nadia.s.bawue.de [193.197.11.52]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA09733; Thu, 18 Mar 1999 21:52:49 +0100 (MET) Received-Date: Thu, 18 Mar 1999 21:52:49 +0100 (MET) Received: from void.s.bawue.de (virtual11.s.bawue.de [193.197.10.11]) by nadia.s.bawue.de (8.9.3/8.9.3) with ESMTP id VAA03872 for ; Thu, 18 Mar 1999 21:52:43 +0100 (CET) Received: from florian by void.s.bawue.de with local (Exim 2.11 #1 (Debian)) id 10NjiQ-0000HP-00; Thu, 18 Mar 1999 21:48:30 +0100 Date: Thu, 18 Mar 1999 21:48:30 +0100 From: Florian Laws To: linux-mips@fnet.fr Subject: Re: Linux on an old Siemens RM400? Message-ID: <19990318214830.B1065@void.s.bawue.de> Mail-Followup-To: linux-mips@fnet.fr References: <19990317205106.A780@void.s.bawue.de> <199903172130.WAA19571@fourier.numerik.math.uni-siegen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199903172130.WAA19571@fourier.numerik.math.uni-siegen.de>; from Michael Engel on Wed, Mar 17, 1999 at 10:30:56PM +0100 Content-Length: 1440 Lines: 46 On Wed, Mar 17, 1999 at 10:30:56PM +0100, Michael Engel wrote: > > Hi, > > > > I have the possibility to get hold of a rather old SNI RM400 server, > > but before I say "Yes, I want to have it" and afterwards am alone > > with a big box of high-tech garbage, I'd like to have some opinions. > > Is it possible to get Linux up and running on this machine? > > Possible yes - done no. There is some support for the RM200C and RM200 > (the PCI and VLB/ISA based MIPS workstations from SNI) but not yet for the > RM400. > I wonder if there is such a thing like _the_ RM400. The last 8 years Siemens surely has changed quite a lot on the hardware side. > > I know that it may need some hacking and even though I've never messed > > with the Linux kernel before I'm willing to try, but is it worth the > > while? > > Hmmm, that depends on what you want to do with the machine ;-). > I don't know. ;-) Just play around with it and a reasnably modern OS on it (read: not the antique SINIX) Of course brag about: "Hey I got a real big fat Dual-MIPS-RM400-Server" ;-)) > > > I know that the information I can give you today is hardly useful and > > I am trying to get some more, what information is important that you > > can help me? > > Before the machine gets thrown away ... if you don't want the machine, let > me know ;-). > Ok, I'll tell you. Thanks, Florian -- I am a signature-virus. Why don't copy me into your sig? From tsbogend@alpha.franken.de Fri Mar 19 00:05:55 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA13216; Fri, 19 Mar 1999 00:05:54 +0100 (MET) Received-Date: Fri, 19 Mar 1999 00:05:54 +0100 (MET) Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id AAA26288; Fri, 19 Mar 1999 00:05:52 +0100 (MET) Received: (from tsbogend@localhost) by alpha.franken.de (8.8.7/8.8.5) id XAA03328 for linux-mips@fnet.fr; Thu, 18 Mar 1999 23:01:26 +0100 Message-ID: <19990318230126.B3281@alpha.franken.de> Date: Thu, 18 Mar 1999 23:01:26 +0100 From: Thomas Bogendoerfer To: linux-mips@fnet.fr Subject: Re: Linux on an old Siemens RM400? References: <19990317205106.A780@void.s.bawue.de> <199903172130.WAA19571@fourier.numerik.math.uni-siegen.de> <19990318214830.B1065@void.s.bawue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <19990318214830.B1065@void.s.bawue.de>; from Florian Laws on Thu, Mar 18, 1999 at 09:48:30PM +0100 Content-Length: 630 Lines: 15 On Thu, Mar 18, 1999 at 09:48:30PM +0100, Florian Laws wrote: > I wonder if there is such a thing like _the_ RM400. the RM400s are still alive. Look at the Siemens web pages. But I guess some of the internals have changed (PCI bus instead of EISA, etc.) Getting running Linux/MIPS on a new MIPS platform is only a matter of getting hardware (most important) and documentation to the right person(s). Thomas. -- This device has completely bogus header. Compaq scores again :-| It's a host bridge, but it should be called ghost bridge instead ;^) [Martin `MJ' Mares on linux-kernel] From ralf@lappi.waldorf-gmbh.de Fri Mar 19 00:07:58 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA13250; Fri, 19 Mar 1999 00:07:56 +0100 (MET) Received-Date: Fri, 19 Mar 1999 00:07:56 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-16.uni-koblenz.de [141.26.131.16]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id AAA10244 for ; Fri, 19 Mar 1999 00:07:30 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id AAA22650; Fri, 19 Mar 1999 00:05:24 +0100 Message-ID: <19990319000524.K19636@uni-koblenz.de> Date: Fri, 19 Mar 1999 00:05:24 +0100 From: ralf@uni-koblenz.de To: Karel van Houten , linux-mips@fnet.fr Cc: linux@engr.sgi.com, linux-mips@vger.rutgers.edu, joey@infodrom.north.de, debian-mips@lists.debian.org, RE-Glaue@wiu.edu Subject: Re: Little Endian - Debian/Linux/MIPS Port References: <199903181752.SAA25644@sparta.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <199903181752.SAA25644@sparta.research.kpn.com>; from Karel van Houten on Thu, Mar 18, 1999 at 06:52:38PM +0100 X-Accept-Language: de,en,fr Content-Length: 1511 Lines: 32 Hi everybody, nice that somebody forwarded this thread to one of the relevant MIPS mailing lists ... I didn't even know about a Debian project, therefore currently the Linux/MIPS FAQ says, there is none ... Anybody wants to write a paragraph about the state, availability etc.? In SGML-Tools, please. > > No Linux Kernel binaries exist for little endian. Whether or not a > > working kernel for little endian can even be cross-compiled for the > > little endian is dependant upon the current maintenance status of the > > Linux kernel source code for linux-mipsel which I do not know. > > So the only thing that those interested in running Linux on little endian > > can do is either cross their fingers and hope things work out with my > > efforts, or help develop a running port of linux on little endian which > > might include cross-compiling and/or kernel hacking. The latter is > > encouraged. > > Also, anyone at all out there who can give me solid information about the > > current maintenance status of linux-mipsel in the Linux Source code, or > > what not, is appreciated. This describes the situation very inaccurate. The kernel binary does not only depend on the machine's byteorder but also on the very much of the rest of the system. So we actually would need to provide several kernel binaries for big and little endian machines. We kernel hackers usually don't because it's alot of work. Aside, I'm running Linux on several big and little endian machines, no prob. Ralf From ralf@lappi.waldorf-gmbh.de Fri Mar 19 00:41:16 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA16147; Fri, 19 Mar 1999 00:40:10 +0100 (MET) Received-Date: Fri, 19 Mar 1999 00:40:10 +0100 (MET) Received: from lappi.waldorf-gmbh.de (cacc-16.uni-koblenz.de [141.26.131.16]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id AAA11381 for ; Fri, 19 Mar 1999 00:40:02 +0100 (MET) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id AAA23460; Fri, 19 Mar 1999 00:38:46 +0100 Message-ID: <19990319003846.O19636@uni-koblenz.de> Date: Fri, 19 Mar 1999 00:38:46 +0100 From: ralf@uni-koblenz.de To: linux@engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu, debian-mips Subject: Re: Little Endian - Debian/Linux/MIPS Port References: <19990316210931.A10315@finlandia.artis.uni-oldenburg.de> <19990318205205.A1101@bun.falkenberg.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <19990318205205.A1101@bun.falkenberg.se>; from Ulf Carlsson on Thu, Mar 18, 1999 at 08:52:05PM -0500 X-Accept-Language: de,en,fr Content-Length: 342 Lines: 8 Talking about the Deskstation Tyne - I dare to bet that it's possible to get the Tyne port running again with a NE2000 card and non-DMA IDE within two days of work. That includes 12h of sleep per day. It will just take somebody competent getting his finger hacking, sigh ... There is even a good reference, the {Net,Open}BSD code. Ralf From ulfc@bun.falkenberg.se Thu Mar 18 21:03:00 1999 Received: from bun.falkenberg.se (dialup89-11-7.swipnet.se [130.244.89.167]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA08443; Thu, 18 Mar 1999 21:02:58 +0100 (MET) Received-Date: Thu, 18 Mar 1999 21:02:58 +0100 (MET) Received: (from ulfc@localhost) by bun.falkenberg.se (8.8.7/8.8.7) id UAA01648; Thu, 18 Mar 1999 20:52:06 -0500 Date: Thu, 18 Mar 1999 20:52:05 -0500 From: Ulf Carlsson To: linux-mips@fnet.fr Cc: debian-mips Subject: Re: Little Endian - Debian/Linux/MIPS Port Message-ID: <19990318205205.A1101@bun.falkenberg.se> Mail-Followup-To: linux-mips@fnet.fr, debian-mips References: <19990316210931.A10315@finlandia.artis.uni-oldenburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: ; from Russell E Glaue on Thu, Mar 18, 1999 at 11:25:46AM -0600 Content-Length: 1752 Lines: 35 On Thu, Mar 18, 1999 at 11:25:46AM -0600, Russell E Glaue wrote: [snip] The little endain MIPS version of Linux works very good, it's just the Deskstation Tyne model which isn't support, not because the processor isn't supported but because none of the kernel developers has such a machine. I've heard from Ralf Baechle that he had such a machine, and therefore there has been support for this machine, but unfortunately his machine didn't boot anylonger a couple of years ago and therefore no one has had the oppertunity to maintain the port to Deskstation Tyne. As the kernel development goes on you break stuff and if you don't fix them they'll remain broken (and myths become to legends which are since long forgotten when..). Well anyway, I think that's what happend to the Tyne. The problem is not that the processor isn't supported, almost all the MIPS processors are supported, even those which run in little endian (the MIPS port was as far as I know initiated for little endain machines). All you will need to do is probably to get the Deskstation Tyne specific hardware running, e.g. the interrupt handler, the prom code and the device drivers. That shouldn't be hard to do once you have the machine in your hands if you're a kernel hacker. :) By the way, look here to find a mipsel kernel binary: ftp://ftp.linux.sgi.com/pub/linux/mips/mipsel-linux/boot And look here to find a complete mipsel redhat distribution: ftp://ftp.linux.sgi.com/pub/linux/mips/mipsel-linux/RPMS (of course that kernel doesn't include Deskstation Tyne support, but it's still little endain mips and you can run those RPMs once you get the kernel up and running... I think) I think there are RPM binaries of cross compilation tools as well somewhere. - Ulf From Harald.Koerfgen@home.ivm.de Fri Mar 19 13:02:53 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA27982; Fri, 19 Mar 1999 13:02:49 +0100 (MET) Received-Date: Fri, 19 Mar 1999 13:02:49 +0100 (MET) Received: from franz.no.dom (port5.koeln.ivm.de [195.247.239.5]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id NAA21194 for ; Fri, 19 Mar 1999 13:02:33 +0100 X-To: Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 19 Mar 1999 13:05:04 +0100 (MET) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: linux-mips@fnet.fr Subject: DECstation bootloader Content-Length: 1704 Lines: 44 Hi all, I wrote: > From what I have been able to find out so far the PROMs load block 0 of > the boot device and depending on the information in there continue to > load blocks in one of the following manners: > > 0) load a number of blocks starting from a start block > > 1) similar to 0 but using a a zero terminated list of (nr_of_blocks, > start_block) ranges. This list has to fit into block 0 which limits this > list to 61 entries. [...] > Another point is, if booting via multiple sequences of blocks really > work, we don't have size restrictions on the bootloader where Ultrix and > *BSD are limited to 7.5 KB, probably for historical reasons. Looks like > time for some further experiments... Ok, I wrote a small and simple utility to assemble such a list of ranges and create a bootsector from that. Then I created a kernel image with "objdump -O binary /usr/src/linux/vmlinux /Image" and invoked "bootprep /Image /dev/sdb" and guess what, it worked! I have been able to boot a whole kernel without any bootloader! This is obviously only a short term solution, but it shows that we can build a "second stage" bootloader of nearly arbitrary size with all the features we want, i.e. deal with different partition tables, different filesystems and different object formats and so on. For those of you who want to play around with this, bootprep.c can be downloaded from ftp.linux.sgi.com/pub/linux/mips/test/. It takes two arguments, the first is the file to be booted which has to be in binary format and the second is the file to which the bootsector is to be written. The load address and the start address of the binary are hardcoded in the source. Have fun. --- Regards, Harald From K.H.C.vanHouten@research.kpn.com Fri Mar 19 19:19:46 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA03142; Fri, 19 Mar 1999 19:19:44 +0100 (MET) Received-Date: Fri, 19 Mar 1999 19:19:44 +0100 (MET) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J90XGER81Y0001GU@research.kpn.com> for linux-mips@fnet.fr; Fri, 19 Mar 1999 19:19:42 +0200 Received: from sparta.research.kpn.com by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id TAA03463; Fri, 19 Mar 1999 19:19:40 +0100 Date: Fri, 19 Mar 1999 19:19:39 +0100 From: "Houten K.H.C. van (Karel)" Subject: Re: DECstation bootloader In-reply-to: "Your message of Fri, 19 Mar 1999 13:05:04 +0100." To: linux-mips@fnet.fr Cc: K.H.C.vanHouten@research.kpn.com Reply-to: K.H.C.vanHouten@research.kpn.com Message-id: <199903191819.TAA03463@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: exmh version 1.6.5 12/11/95 Content-type: text/plain; charset=us-ascii X-Face: ";:TzQQC{mTp~$W,'m4@Lu1Lu$rtG_~5kvYO~F:C'KExk9o1X"iRz[0%{bq?6Aj#>VhSD?v 1W9`.Qsf+P&*iQEL8&y,RDj&U.]!(R-?c-h5h%Iw%r$|%6+Jc>GTJe!_1&A0o'lC[`I#={2BzOXT1P q366I$WL=;[+SDo1RoIT+a}_y68Y:jQ^xp4=*4-ryiymi>hy Content-Length: 1736 Lines: 48 Harald Koerfgen wrote: > Ok, I wrote a small and simple utility to assemble such a list of ranges > and create a bootsector from that. Then I created a kernel image with > "objdump -O binary /usr/src/linux/vmlinux /Image" and invoked "bootprep > /Image /dev/sdb" and guess what, it worked! > > I have been able to boot a whole kernel without any bootloader! > > This is obviously only a short term solution, but it shows that we can > build a "second stage" bootloader of nearly arbitrary size with all the > features we want, i.e. deal with different partition tables, different > filesystems and different object formats and so on. > > For those of you who want to play around with this, bootprep.c can be > downloaded from ftp.linux.sgi.com/pub/linux/mips/test/. It takes two > arguments, the first is the file to be booted which has to be in binary > format and the second is the file to which the bootsector is to be > written. The load address and the start address of the binary are > hardcoded in the source. I tried this, and promptly I erased my partition table from my disk :-(. I'll have to recreate that tomorrow. I think Harald meant "objcopy -O binary /usr/src/linux/vmlinux /Image", not objdump. Harald, what type of partition table do you use? your program bootprep program produces 512 bytes of output, so many partition tables might be damaged. After that minor disaster, I tried to boot 'boot 3/rz0', but the system just resets. Any hints? Regards, Karel. -- Karel van Houten ---------------------------------------------------------- The box said "Requires Windows 95 or better." I can't understand why it won't work on my Linux computer. ---------------------------------------------------------- From Harald.Koerfgen@home.ivm.de Sat Mar 20 12:00:02 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA11936; Sat, 20 Mar 1999 12:00:00 +0100 (MET) Received-Date: Sat, 20 Mar 1999 12:00:00 +0100 (MET) Received: from franz.no.dom (port56.koeln.ivm.de [195.247.239.56]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id LAA18157; Sat, 20 Mar 1999 11:59:52 +0100 X-To: linux-mips@fnet.fr Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903191819.TAA03463@sparta.research.kpn.com> Date: Sat, 20 Mar 1999 12:02:23 +0100 (MET) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: linux-mips@fnet.fr Subject: Re: DECstation bootloader Cc: K.H.C.vanHouten@research.kpn.com Content-Length: 1305 Lines: 48 Hi Karel and all, On 19-Mar-99 Houten K.H.C. van (Karel) wrote: > > Harald Koerfgen wrote: [some stuff snipped] >> I have been able to boot a whole kernel without any bootloader! > I tried this, and promptly I erased my partition table from my disk :-(. > I'll have to recreate that tomorrow. Sorry about that, Karel. I've tried bootprep on a disk without any partition table and had no problems. > I think Harald meant "objcopy -O binary /usr/src/linux/vmlinux /Image", > not objdump. Oops, you're right. > Harald, what type of partition table do you use? your program bootprep > program produces 512 bytes of output, so many partition tables > might be damaged. Have you been using NetBSD and can it be that NetBSD stores partition information in sector 0? If so, then NetBSD is on the wrong track because sector 0 belongs to the PROM. Period. > After that minor disaster, I tried to boot 'boot 3/rz0', but the system > just resets. > > Any hints? Please make shure that boot_block->loadAddr and boot_block->execAddr (lines 150 and 151 of bootprep.c) correspond to LOADADDR and kernel_entry and do _not_ use nbImage _but_ vmlinux for bootprep. I've tested bootprep on my /133 in the meantime and it works as well. FYI: /260: KN05 V2.1k /133: KN02-BA V5.7j Have fun. --- Regards, Harald From K.H.C.vanHouten@research.kpn.com Sat Mar 20 12:11:58 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA12910; Sat, 20 Mar 1999 12:11:57 +0100 (MET) Received-Date: Sat, 20 Mar 1999 12:11:57 +0100 (MET) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J91WTDHFTU0000UR@research.kpn.com> for linux-mips@fnet.fr; Sat, 20 Mar 1999 12:11:55 +0200 Received: by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id MAA23279; Sat, 20 Mar 1999 12:11:54 +0100 X-URL: http://www-lsdm.research.kpn.com/~karel Date: Sat, 20 Mar 1999 12:11:54 +0100 (MET) From: K.H.C.vanHouten@research.kpn.com (Karel van Houten) Subject: Re: DECstation bootloader In-reply-to: To: linux-mips@fnet.fr Cc: K.H.C.vanHouten@research.kpn.com (Houten K.H.C. van ) Message-id: <199903201111.MAA23279@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-Length: 758 Lines: 26 Hi Harald, You wrote: > ... > Have you been using NetBSD and can it be that NetBSD stores partition > information in sector 0? > > If so, then NetBSD is on the wrong track because sector 0 belongs to the > PROM. Period. > What partition table format leaves sector 0 for the PROM? As far as I know MSDOS, NetBSD, SUN, all use the first sector for partition info. If we really need the whole first sector for the bootloader, we have to create a new partition table format, which I would not like. Regards, -- Karel van Houten ---------------------------------------------------------- The box said "Requires Windows 95 or better." I can't understand why it won't work on my Linux computer. ---------------------------------------------------------- From RE-Glaue@wiu.edu Mon Mar 22 02:49:14 1999 Received: from uxa.ecn.bgu.edu (root@uxa.ecn.bgu.edu [143.43.32.11]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA02381; Mon, 22 Mar 1999 02:49:12 +0100 (MET) Received-Date: Mon, 22 Mar 1999 02:49:12 +0100 (MET) Received: from ecom5.ecnet.net (mureg3@ecom5 [143.43.32.25]) by uxa.ecn.bgu.edu (8.8.2/8.8.2) with ESMTP id TAA06421; Sun, 21 Mar 1999 19:48:35 -0600 (CST) Received: from localhost (mureg3@localhost) by ecom5.ecnet.net (8.8.8/8.8.8) with SMTP id TAA28468; Sun, 21 Mar 1999 19:48:22 -0600 (CST) X-Authentication-Warning: ecom5.ecnet.net: mureg3 owned process doing -bs Date: Sun, 21 Mar 1999 19:48:22 -0600 (CST) From: Russell E Glaue X-Sender: mureg3@ecom5 Reply-To: Russell E Glaue To: Karel van Houten cc: linux-mips@fnet.fr, linux@engr.sgi.com, linux-mips@vger.rutgers.edu, joey@infodrom.north.de, debian-mips@lists.debian.org Subject: Re: Little Endian - Debian/Linux/MIPS Port In-Reply-To: <199903181752.SAA25644@sparta.research.kpn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2123 Lines: 55 Yes, I have seen the DECstation site, but I do not own a DECstation system. What my work place has are Deskstation Mainboards with the MIPS R4600 processor. Is the DECstation port compatible with the Deskstation bios and related system chipset and hardware? I didn't think it was. -----russ----- :|Hi Russ, :| :|Have a look at the DECStation linux port pages at: :| :|http://decstation.unix-ag.org/ or at my personal decstation page at: :| :|http://www.xs4all.nl/~vhouten/mipsel/ (more up-to-date). :| :|This is a Little Endian port of Linux for R3000 / R4000 DECStations. :| :|Russ wrote: :|> :|> :|> In Summary. :|> No Linux Kernel binaries exist for little endian. Whether or not a :|> working kernel for little endian can even be cross-compiled for the :|> little endian is dependant upon the current maintenance status of the :|> Linux kernel source code for linux-mipsel which I do not know. :|> So the only thing that those interested in running Linux on little endian :|> can do is either cross their fingers and hope things work out with my :|> efforts, or help develop a running port of linux on little endian which :|> might include cross-compiling and/or kernel hacking. The latter is :|> encouraged. :|> Also, anyone at all out there who can give me solid information about the :|> current maintenance status of linux-mipsel in the Linux Source code, or :|> what not, is appreciated. :|> -----russ----- :| :|-- :|Karel van Houten :| :|---------------------------------------------------------- :|The box said "Requires Windows 95 or better." :|I can't understand why it won't work on my Linux computer. :|---------------------------------------------------------- :| :| +------------------------------------------+ -----russ----- |--- Russell E. Glaue ( re-glaue@wiu.edu ) | |--- rglaue@ccinyc.com +----------+--------+------+ I'm a Music Major, and |--- http://www.wiu.edu/users/mureg3/homepage.htm | that's my only excuse. +-------------------------------------------------+ ---------------------- Support Fine Arts Education in the USA. http://www.AMC-Music.com From RE-Glaue@wiu.edu Mon Mar 22 03:01:16 1999 Received: from uxa.ecn.bgu.edu (root@uxa.ecn.bgu.edu [143.43.32.11]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id DAA02933; Mon, 22 Mar 1999 03:01:13 +0100 (MET) Received-Date: Mon, 22 Mar 1999 03:01:13 +0100 (MET) Received: from ecom5.ecnet.net (mureg3@ecom5 [143.43.32.25]) by uxa.ecn.bgu.edu (8.8.2/8.8.2) with ESMTP id UAA07665; Sun, 21 Mar 1999 20:00:52 -0600 (CST) Received: from localhost (mureg3@localhost) by ecom5.ecnet.net (8.8.8/8.8.8) with SMTP id UAA28960; Sun, 21 Mar 1999 20:00:39 -0600 (CST) X-Authentication-Warning: ecom5.ecnet.net: mureg3 owned process doing -bs Date: Sun, 21 Mar 1999 20:00:39 -0600 (CST) From: Russell E Glaue X-Sender: mureg3@ecom5 Reply-To: Russell E Glaue To: ralf@uni-koblenz.de cc: linux-mips@fnet.fr, linux@engr.sgi.com, linux-mips@vger.rutgers.edu, joey@infodrom.north.de, debian-mips@lists.debian.org Subject: Re: Little Endian - Debian/Linux/MIPS Port In-Reply-To: <19990319000524.K19636@uni-koblenz.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2393 Lines: 53 What system configuration(s) are you running little endian on? I am aware of ports to systems like DECstation and sparse out-dated (kernel 2.0.2x) support for Deskstation Tyne and other systems. I am not aware of any current support for little endian, and in particular for the Deskstation Tyne (the system I have access to). -----russ----- On Fri, 19 Mar 1999 ralf@uni-koblenz.de wrote: :| :|Hi everybody, :| :|nice that somebody forwarded this thread to one of the relevant MIPS :|mailing lists ... I didn't even know about a Debian project, therefore :|currently the Linux/MIPS FAQ says, there is none ... :| :|Anybody wants to write a paragraph about the state, availability etc.? :|In SGML-Tools, please. :| :|> > No Linux Kernel binaries exist for little endian. Whether or not a :|> > working kernel for little endian can even be cross-compiled for the :|> > little endian is dependant upon the current maintenance status of the :|> > Linux kernel source code for linux-mipsel which I do not know. :|> > So the only thing that those interested in running Linux on little endian :|> > can do is either cross their fingers and hope things work out with my :|> > efforts, or help develop a running port of linux on little endian which :|> > might include cross-compiling and/or kernel hacking. The latter is :|> > encouraged. :|> > Also, anyone at all out there who can give me solid information about the :|> > current maintenance status of linux-mipsel in the Linux Source code, or :|> > what not, is appreciated. :| :|This describes the situation very inaccurate. The kernel binary does not :|only depend on the machine's byteorder but also on the very much of the :|rest of the system. So we actually would need to provide several kernel :|binaries for big and little endian machines. We kernel hackers usually :|don't because it's alot of work. :| :|Aside, I'm running Linux on several big and little endian machines, no :|prob. :| :| Ralf :| :| +------------------------------------------+ -----russ----- |--- Russell E. Glaue ( re-glaue@wiu.edu ) | |--- rglaue@ccinyc.com +----------+--------+------+ I'm a Music Major, and |--- http://www.wiu.edu/users/mureg3/homepage.htm | that's my only excuse. +-------------------------------------------------+ ---------------------- Support Fine Arts Education in the USA. http://www.AMC-Music.com From imp@harmony.village.org Mon Mar 22 03:34:53 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id DAA04856; Mon, 22 Mar 1999 03:34:50 +0100 (MET) Received-Date: Mon, 22 Mar 1999 03:34:50 +0100 (MET) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id CAA98028; Mon, 22 Mar 1999 02:33:54 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA00474; Sun, 21 Mar 1999 19:33:23 -0700 (MST) Message-Id: <199903220233.TAA00474@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: Little Endian - Debian/Linux/MIPS Port Cc: Karel van Houten , linux@engr.sgi.com, linux-mips@vger.rutgers.edu, joey@infodrom.north.de, debian-mips@lists.debian.org In-reply-to: Your message of "Sun, 21 Mar 1999 19:48:22 CST." References: Date: Sun, 21 Mar 1999 19:33:23 -0700 From: Warner Losh Content-Length: 782 Lines: 17 In message Russell E Glaue writes: : Is the DECstation port compatible with the Deskstation bios and related : system chipset and hardware? I didn't think it was. Deskstation and DECstation are two different beasties. The Deskstation Tyne (and rPC44, which is my machine) are both R4xxx based machines that use the ARC BIOS interface. All ARC BIOS machines are little endian (well, sgi calls its bios ARC too, so that is confusing). The JAZZ is supported as a ARC BIOS machine and it is little endian. Ralf also has several other little endian mips machines that he's supporting. The Tyne isn't one of them due to hardware problems with the one he had and some bone-headedness, at the time, on the part of Deskstation. Warner From cddeyounNO---SPAMMMM@rconnect.com Mon Mar 22 05:35:40 1999 Received: from rconnect.com (ns1.rconnect.com [206.144.249.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id FAA07227; Mon, 22 Mar 1999 05:35:38 +0100 (MET) Received-Date: Mon, 22 Mar 1999 05:35:38 +0100 (MET) Received: from goldfinger (pmroch7-132.rconnect.com [209.163.9.132]) by rconnect.com (8.9.1a/8.9.1) with SMTP id WAA21829 for ; Sun, 21 Mar 1999 22:35:34 -0600 (CST) Message-ID: <000701be741d$9b28f9a0$0101a8c0@goldfinger.rconnect.com> From: "Chris DeYoung" To: Subject: Linux on the Casiopeia? Date: Sun, 21 Mar 1999 22:36:48 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01BE73EB.4ED986A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Content-Length: 1990 Lines: 58 This is a multi-part message in MIME format. ------=_NextPart_000_0004_01BE73EB.4ED986A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, I just bought a casiopeia e-11 a few weeks ago. Has anyone toyed with = getting a kernel to boot on one of these things? I see the R4000 is = supported on another box.=20 Chris DeYoung K-Lug Rochester MN Linux Users Group www.pcxtreme.org/linux ------=_NextPart_000_0004_01BE73EB.4ED986A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi all,
 I just bought a casiopeia e-11 = a few weeks=20 ago. Has anyone toyed with getting a kernel to boot on one of these = things? I=20 see the R4000 is supported on another box.
 
          &nbs= p;    =20 Chris DeYoung
          &nbs= p;    =20 K-Lug
          &nbs= p;    =20 Rochester MN Linux Users Group
          &nbs= p;    =20 www.pcxtreme.org/linux<= /DIV> ------=_NextPart_000_0004_01BE73EB.4ED986A0-- From imp@harmony.village.org Mon Mar 22 07:45:59 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id HAA10917; Mon, 22 Mar 1999 07:45:56 +0100 (MET) Received-Date: Mon, 22 Mar 1999 07:45:56 +0100 (MET) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id GAA98784 for ; Mon, 22 Mar 1999 06:45:48 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA01748 for ; Sun, 21 Mar 1999 23:45:18 -0700 (MST) Message-Id: <199903220645.XAA01748@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: Linux on the Casiopeia? In-reply-to: Your message of "Sun, 21 Mar 1999 22:36:48 CST." <000701be741d$9b28f9a0$0101a8c0@goldfinger.rconnect.com> References: <000701be741d$9b28f9a0$0101a8c0@goldfinger.rconnect.com> Date: Sun, 21 Mar 1999 23:45:18 -0700 From: Warner Losh Content-Length: 1084 Lines: 22 In message <000701be741d$9b28f9a0$0101a8c0@goldfinger.rconnect.com> "Chris DeYoung" writes: : I just bought a casiopeia e-11 a few weeks ago. Has anyone toyed with : getting a kernel to boot on one of these things? I see the R4000 is : supported on another box. When WinCE boxes say that theyare R4000, it means that the CPU implements the MIPS ISA, more or less, and it isn't more specific. The E-11 that you got has a Vr4111 in it, which would take a little bit of hacking to make work. Its config and status registers are a little different than other R4xxx cpus, but in a mostly compatible way (kinda sort, if you don't count secondary cache). The hardest part is bootstrapping. Since these devices have ROM (not eeprom, eprom or flash) in them, you have to do an end run around WinCE. Fortunately, there is a wince loader in the works. My WinCE boxes were damaged beyond repair, so I've put my efforts to get a Free OS running on them on indefinite hold. The machines still kinda work, but would only make good routers and such since the screens are smashed. :-( Warner From florian@void.s.bawue.de Tue Mar 23 22:22:52 1999 Received: from nadia.s.bawue.de (root@nadia.s.bawue.de [193.197.11.52]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA01913; Tue, 23 Mar 1999 22:22:50 +0100 (MET) Received-Date: Tue, 23 Mar 1999 22:22:50 +0100 (MET) Received: from void.s.bawue.de (virtual14.s.bawue.de [193.197.10.14]) by nadia.s.bawue.de (8.9.3/8.9.3) with ESMTP id WAA08805 for ; Tue, 23 Mar 1999 22:22:30 +0100 (CET) Received: from florian by void.s.bawue.de with local (Exim 2.11 #1 (Debian)) id 10PYD8-00004l-00; Tue, 23 Mar 1999 21:55:42 +0100 Date: Tue, 23 Mar 1999 21:55:42 +0100 From: Florian Laws To: linux-mips@fnet.fr Subject: Re: Linux on an old Siemens RM400? Message-ID: <19990323215542.A288@void.s.bawue.de> Mail-Followup-To: linux-mips@fnet.fr References: <19990317205106.A780@void.s.bawue.de> <199903172130.WAA19571@fourier.numerik.math.uni-siegen.de> <19990318214830.B1065@void.s.bawue.de> <19990318230126.B3281@alpha.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990318230126.B3281@alpha.franken.de>; from Thomas Bogendoerfer on Thu, Mar 18, 1999 at 11:01:26PM +0100 Content-Length: 1225 Lines: 32 On Thu, Mar 18, 1999 at 11:01:26PM +0100, Thomas Bogendoerfer wrote: > On Thu, Mar 18, 1999 at 09:48:30PM +0100, Florian Laws wrote: > > I wonder if there is such a thing like _the_ RM400. > > the RM400s are still alive. Look at the Siemens web pages. But I guess > some of the internals have changed (PCI bus instead of EISA, etc.) > That's what I meant when I said _the_ one RM400 doensn't exist. ;-) > Getting running Linux/MIPS on a new MIPS platform is only a matter of > getting hardware (most important) and documentation to the right person(s). > Pity I can get only one machine and I'd like to keep it for myself. ;-)) So I suppose I have to become a kind of kernel hacker myself. I hope it doesn't hurt too bad. ;-\ Speaking of documentation: When I was on the CeBIT in Hannover, I asked the RM400 people at the Siemens booth for developer documentation and they told me that documentation should be shipped with the machine. Is Siemens documentation _that_ comprehensive or didn't the salesmen realize what kind of docu I was asking for? Thanks, Florian -- "A user interface geek is someone geeky enough to realize what the nongeeks want to work with." --Dan Kaminsky on samba-ntdom From tsbogend@alpha.franken.de Wed Mar 24 01:18:34 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA04696; Wed, 24 Mar 1999 01:18:33 +0100 (MET) Received-Date: Wed, 24 Mar 1999 01:18:33 +0100 (MET) Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id BAA22268; Wed, 24 Mar 1999 01:18:30 +0100 (MET) Received: (from tsbogend@localhost) by alpha.franken.de (8.8.7/8.8.5) id AAA03192 for linux-mips@fnet.fr; Wed, 24 Mar 1999 00:55:34 +0100 Message-ID: <19990324005534.B3168@alpha.franken.de> Date: Wed, 24 Mar 1999 00:55:34 +0100 From: Thomas Bogendoerfer To: linux-mips@fnet.fr Subject: Re: Linux on an old Siemens RM400? References: <19990317205106.A780@void.s.bawue.de> <199903172130.WAA19571@fourier.numerik.math.uni-siegen.de> <19990318214830.B1065@void.s.bawue.de> <19990318230126.B3281@alpha.franken.de> <19990323215542.A288@void.s.bawue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <19990323215542.A288@void.s.bawue.de>; from Florian Laws on Tue, Mar 23, 1999 at 09:55:42PM +0100 Content-Length: 1015 Lines: 25 On Tue, Mar 23, 1999 at 09:55:42PM +0100, Florian Laws wrote: > Pity I can get only one machine and I'd like to keep it for myself. ;-)) A loaner for some time (1-3 months, depends on docs and already available Linux drivers for the hardware) to get the hard work done, would be enough. > So I suppose I have to become a kind of kernel hacker myself. > I hope it doesn't hurt too bad. ;-\ I prefer kernel hacking over user level stuff. It's the special kick to know, that a wrong line of code can crash the system, burn the CPU and toast every hard drive in the system:-)) > Is Siemens documentation _that_ comprehensive or didn't the salesmen realize > what kind of docu I was asking for? I would guess the salesmen couldn't imagine what type of documentation you're looking for. Thomas. -- This device has completely bogus header. Compaq scores again :-| It's a host bridge, but it should be called ghost bridge instead ;^) [Martin `MJ' Mares on linux-kernel] From ssibert@hollins.edu Wed Mar 24 22:33:10 1999 Received: from jane.hollins.edu (jane.hollins.EDU [192.160.94.78]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id WAA12834; Wed, 24 Mar 1999 22:33:09 +0100 (MET) Received-Date: Wed, 24 Mar 1999 22:33:09 +0100 (MET) Received: from Kira.hollins.edu by jane.hollins.edu (5.65v4.0/1.1.8.2/04Jan96-0223PM) id AA00917; Wed, 24 Mar 1999 16:34:01 -0500 Received: from tuvok.hollins.edu (Tuvok.hollins.edu [192.160.94.64]) by kira.hollins.edu (8.8.7/8.8.7) with ESMTP id QAA31240 for ; Wed, 24 Mar 1999 16:41:13 -0500 Message-Id: <199903242141.QAA31240@kira.hollins.edu> Date: Wed, 24 Mar 1999 16:37:46 -0500 Sender: ssibert From: ssibert To: linux-mips@fnet.fr Subject: Linux MIPS Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7BIT X-Mailer: WebMail (Hydra) SMTP v3.50 Content-Length: 418 Lines: 15 Hello. Is this address still valid for Linux on MIPS? I have a DECstation 5000/260 (r4400) with 128mb memory and I would love to get Linux running on it. I also have a Personal DECstation. I'm currently running Linux on a 486, a P100, a Cyrix P166+, and an AMD K6-2 333 (3dnow!) and I know a decent amount about Linux. Thank you. Scott A. Sibert Assistant Director of Networking and Systems Hollins University From Harald.Koerfgen@home.ivm.de Wed Mar 24 23:51:46 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA14148; Wed, 24 Mar 1999 23:51:44 +0100 (MET) Received-Date: Wed, 24 Mar 1999 23:51:44 +0100 (MET) Received: from franz.no.dom (port27.koeln.ivm.de [195.247.239.27]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id XAA21918; Wed, 24 Mar 1999 23:51:26 +0100 X-To: linux-mips@fnet.fr Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903242141.QAA31240@kira.hollins.edu> Date: Wed, 24 Mar 1999 23:54:02 +0100 (MET) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: ssibert Subject: RE: Linux MIPS Cc: linux-mips@fnet.fr Content-Length: 1142 Lines: 42 Hello Scott, On 24-Mar-99 ssibert wrote: > Hello. > > Is this address still valid for Linux on MIPS? Yes, it is. > I have a DECstation 5000/260 (r4400) with 128mb memory and I would love > to get Linux running on it. I also have a Personal DECstation. you may want to give ftp://ftp.linux.sgi.com/pub/linux/mips/test/linux-2.2.1-dec.tar.gz a try. Altough still in a *very* experimental state we have serial console, networking and SCSI running, well, sort of :-). This source tree should work on both but Linux/MIPS isn't generic yet, i.e. you have to make shure to compile this source tree for the right target CPU. > I'm currently running Linux on a 486, a P100, a Cyrix P166+, and an AMD > K6-2 > 333 (3dnow!) and I know a decent amount about Linux. If your i386 boxen are glibc based you can get an crosscompiling environment from ftp://bolug.uni-bonn.de/mips/ and additional information is available via: http://decstation.unix-ag.org http://www.xs4all.nl/~vhouten/mipsel/ ftp://ftp.linux.sgi.com/cvs/faq/mips-howto.sgml,v > Thank you. Never mind. If you have further questions, feel free to ask me. --- Regards, Harald From joey@finlandia.Infodrom.North.DE Thu Mar 25 16:21:52 1999 Received: from gimli.Informatik.Uni-Oldenburg.DE (gimli.Informatik.Uni-Oldenburg.DE [134.106.1.10]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id QAA25422; Thu, 25 Mar 1999 16:21:19 +0100 (MET) Received-Date: Thu, 25 Mar 1999 16:21:19 +0100 (MET) Received: from finlandia.Infodrom.North.DE ([134.106.121.3]) by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.29.1) id ; Thu, 25 Mar 99 16:19 CET Received: at Infodrom Oldenburg (/\##/\ Smail-3.2.0.102 1998-Aug-2 #2) by finlandia.Infodrom.North.DE via smail from stdin id for RE-Glaue@wiu.edu; Thu, 25 Mar 1999 16:19:23 +0100 (CET) Date: Thu, 25 Mar 1999 16:19:23 +0100 From: Martin Schulze To: ralf@uni-koblenz.de Cc: Karel van Houten , linux-mips@fnet.fr, linux@engr.sgi.com, linux-mips@vger.rutgers.edu, debian-mips@lists.debian.org, RE-Glaue@wiu.edu Subject: Re: Little Endian - Debian/Linux/MIPS Port Message-ID: <19990325161923.E11039@finlandia.artis.uni-oldenburg.de> Reply-To: Martin Schulze References: <199903181752.SAA25644@sparta.research.kpn.com> <19990319000524.K19636@uni-koblenz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990319000524.K19636@uni-koblenz.de>; from ralf@uni-koblenz.de on Fri, Mar 19, 1999 at 12:05:24AM +0100 Content-Length: 752 Lines: 30 ralf@uni-koblenz.de wrote: > Hi everybody, > > nice that somebody forwarded this thread to one of the relevant MIPS > mailing lists ... I didn't even know about a Debian project, therefore > currently the Linux/MIPS FAQ says, there is none ... Which is still true. > Anybody wants to write a paragraph about the state, availability etc.? > In SGML-Tools, please. Well that's easy. Here it is: "" Up to now there are only some attempts made. I hope that some of the people who own a MIPS machine - I don't have one yet and even if I would I could only hook it on the net but not hack on it due to my time constraints. Regards, Joey -- The only stupid question is the unasked one. Please always Cc to me when replying to me on the lists. From matthias@peick.com Thu Mar 25 23:11:04 1999 Received: from teik.halut (root@Isis226.urz.uni-duesseldorf.de [134.99.138.226]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA28948; Thu, 25 Mar 1999 23:08:47 +0100 (MET) Received-Date: Thu, 25 Mar 1999 23:08:47 +0100 (MET) Received: (from matthias@localhost) by teik.halut (8.8.8/8.8.8) id TAA00312; Thu, 25 Mar 1999 19:25:23 +0100 To: linux-mips@fnet.fr Subject: Re: ADV: 4000 Years of Design at Your Fingertips References: <199903250532.GAA02902@diablo> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-No-Archive: yes From: Matthias Peick Date: 25 Mar 1999 19:25:23 +0100 In-Reply-To: 's message of Thu, 25 Mar 1999 06:32:14 +0100 Message-ID: X-Mailer: Gnus v5.5/Emacs 20.2 Content-Length: 113 Lines: 8 <@peick.com> writes: [spam] Sorry, it's not from me. -- Manche Erkenntnis verliert mit der Zeit an Klarheit. From Harald.Koerfgen@home.ivm.de Sun Mar 28 19:23:43 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA26250; Sun, 28 Mar 1999 19:23:42 +0200 (MET DST) Received-Date: Sun, 28 Mar 1999 19:23:42 +0200 (MET DST) Received: from franz.no.dom (port36.koeln.ivm.de [195.247.239.36]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id TAA05552; Sun, 28 Mar 1999 19:23:25 +0200 X-To: linux-mips@fnet.fr Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903201111.MAA23279@sparta.research.kpn.com> Date: Sun, 28 Mar 1999 18:26:02 +0200 (MEST) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: linux-mips@fnet.fr Subject: Re: DECstation bootloader Cc: (Houten K.H.C. van) Content-Length: 2602 Lines: 71 Hi Karel, On 20-Mar-99 Karel van Houten wrote: > Hi Harald, > > You wrote: >> ... >> Have you been using NetBSD and can it be that NetBSD stores partition >> information in sector 0? >> >> If so, then NetBSD is on the wrong track because sector 0 belongs to >> the >> PROM. Period. >> > > What partition table format leaves sector 0 for the PROM? As far as I > know > MSDOS, NetBSD, SUN, all use the first sector for partition info. > > If we really need the whole first sector for the bootloader, we have to > create a new partition table format, which I would not like. Well, I don't like this too. On the other hand, I don't see any benefit from writing bootblocks or a two stage boot process when the PROM is able to handle this nicely for us. I agree, not storing partition tables in the boot block, like Ultrix does, is not a very good idea. What we want to have is as much room as possible for boot maps and, as a result, partition tables as small as possible. The NetBSD partion tables are far to big for that, so the NetBSD way isn't a good idea as well. An alternative could be using slightly modified sun partition tables. My proposal for the layout for the bootblock is: typedef struct Dec_BootMap { int numBlocks; /* Number of blocks to read. */ int startBlock; /* Starting block on disk. */ } Dec_BootMap; struct Dec_DiskBoot { char spare1[8]; int magic; /* DEC_BOOT_MAGIC */ int mode; /* Mode for boot info. */ int loadAddr; /* Address to start loading. */ int execAddr; /* Address to start execing. */ Dec_BootMap map[51]; /* Position of boot program. */ unsigned short ncyl; /* Data cylinder count */ unsigned short nacyl; /* Alt. cylinder count */ unsigned short ntrks; /* Tracks per cylinder */ unsigned short nsect; /* Sectors per track */ unsigned char spare3[4]; /* Even more magic... */ struct sun_partition { __u32 start_cylinder; __u32 num_sectors; } partitions[8]; unsigned short magic; /* Magic number */ unsigned short csum; /* Label xor'd checksum */ } Dec_DiskBoot; That is enough that the Kernel recognises the sun partition table without modification and leaves enough room for 51 boot maps which, even in the worst case, is suitable for a 51 KB bootloader. The only drawback is that fdisk needs to modified to deal with the modified sun partition tables. Comments? --- Regards, Harald From rraffer1@osf1.gmu.edu Sun Mar 28 20:30:33 1999 Received: from osf1.gmu.edu (osf1.gmu.edu [129.174.1.13]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id UAA26600; Sun, 28 Mar 1999 20:30:32 +0200 (MET DST) Received-Date: Sun, 28 Mar 1999 20:30:32 +0200 (MET DST) Received: from localhost (rraffer1@localhost) by osf1.gmu.edu (8.8.8/8.8.8) with SMTP id NAA08554 for ; Sun, 28 Mar 1999 13:30:29 -0500 (EST) Date: Sun, 28 Mar 1999 13:30:29 -0500 (EST) From: Ryan Rafferty Reply-To: Ryan Rafferty To: linux-mips@fnet.fr Subject: MIPS Magnum update In-Reply-To: <19990324005534.B3168@alpha.franken.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1074 Lines: 24 For the first time, my MIPS Magnum has its onboard SONIC ethernet adapter recognized by the kernel, using Thomas Bogendoerfer's 2.2.1 kernel for the Olivetti M700. This is good news because the ethernet adapter was not recognized by the 2.1.99 kernel, though it worked for the M700. However, after the "freeing unused memory" and "mounting root" messages the boot process halts without starting INIT. I believe that is because I am using the old root-2 disk image plus some older RPMS for a boot disk; am I correct in assuming that I need to update the root image for use with newer kernels? If so, can I use the RPMS from intel.cleveland.lug.net:/pub/Mipsel/RPMS (compiled for the Cobalt Qube) or must I use the RPMS for DECStations? Once I get a working userland I will try to find the source for the Linux framebuffer X-server and see if it compiles on MIPS (or has this already been accomplished?). Between FB compatibility on the G364 provided by Thomas and the standard PS/2 mouse on the Magnum I hope to have X running smoothly soon. Thanks, Ryan Rafferty From imp@harmony.village.org Sun Mar 28 21:46:38 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA27183; Sun, 28 Mar 1999 21:46:36 +0200 (MET DST) Received-Date: Sun, 28 Mar 1999 21:46:36 +0200 (MET DST) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id TAA02082; Sun, 28 Mar 1999 19:46:18 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA22821; Sun, 28 Mar 1999 12:45:42 -0700 (MST) Message-Id: <199903281945.MAA22821@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: DECstation bootloader Cc: K.H.C.vanHouten@research.kpn.com (Houten K.H.C. van) In-reply-to: Your message of "Sun, 28 Mar 1999 18:26:02 +0200." References: Date: Sun, 28 Mar 1999 12:45:42 -0700 From: Warner Losh Content-Length: 749 Lines: 16 In message Harald Koerfgen writes: : Well, I don't like this too. On the other hand, I don't see any benefit : from writing bootblocks or a two stage boot process when the PROM is able : to handle this nicely for us. You might want to look into the new bootblocks that were just committed to the NetBSD tree. They are quite powerful. You will likely not be able to get the PROMs to do everything you want on the DECstations. The NetBSD folks have been dealing with the boot problem for literally years and likely have an excellent grasp on all the subtle issues involve. No slight intened against the people working on this, but I really hate to see the wheel reinvented yet again :-(. Warner From Harald.Koerfgen@home.ivm.de Sun Mar 28 23:25:22 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA27751; Sun, 28 Mar 1999 23:25:20 +0200 (MET DST) Received-Date: Sun, 28 Mar 1999 23:25:20 +0200 (MET DST) Received: from franz.no.dom (port9.koeln.ivm.de [195.247.239.9]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id XAA16753; Sun, 28 Mar 1999 23:25:07 +0200 X-To: linux-mips@fnet.fr Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 28 Mar 1999 22:27:44 +0200 (MEST) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: Ryan Rafferty Subject: RE: MIPS Magnum update Cc: linux-mips@fnet.fr Content-Length: 842 Lines: 28 Hi Ryan, On 28-Mar-99 Ryan Rafferty wrote: > However, after the "freeing unused memory" and "mounting root" messages > the boot process halts without starting INIT. I believe that is because > I > am using the old root-2 disk image plus some older RPMS for a boot disk; > am I correct in assuming that I need to update the root image for use > with > newer kernels? If so, can I use the RPMS from > intel.cleveland.lug.net:/pub/Mipsel/RPMS (compiled for the Cobalt Qube) > or > must I use the RPMS for DECStations? Well, that's one of the advantages of Linux/MIPS, binary compatibility. You can use both :-). Just in case you're having troubles with your root filesystem, ftp://ftp.linux.sgi.com/pub/linux/mips/mipsel/root/declinuxroot-990128.tgz might be a good start for a more up to date one. Happy hacking. --- Regards, Harald From ralf@lappi.waldorf-gmbh.de Sun Mar 28 23:39:26 1999 Received: from mailhost.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.64.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA27843; Sun, 28 Mar 1999 23:39:23 +0200 (MET DST) Received-Date: Sun, 28 Mar 1999 23:39:23 +0200 (MET DST) Received: from lappi.waldorf-gmbh.de (cacc-1.uni-koblenz.de [141.26.131.1]) by mailhost.uni-koblenz.de (8.9.1/8.9.1) with ESMTP id XAA16453 for ; Sun, 28 Mar 1999 23:39:17 +0200 (MET DST) Received: (from ralf@localhost) by lappi.waldorf-gmbh.de (8.8.7/8.8.7) id XAA02421 for linux-mips@fnet.fr; Sun, 28 Mar 1999 23:39:01 +0200 Message-ID: <19990328233901.B526@uni-koblenz.de> Date: Sun, 28 Mar 1999 23:39:01 +0200 From: ralf@uni-koblenz.de To: linux-mips@fnet.fr Subject: Re: MIPS Magnum update References: <19990324005534.B3168@alpha.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Ryan Rafferty on Sun, Mar 28, 1999 at 01:30:29PM -0500 X-Accept-Language: de,en,fr Content-Length: 1121 Lines: 25 On Sun, Mar 28, 1999 at 01:30:29PM -0500, Ryan Rafferty wrote: > However, after the "freeing unused memory" and "mounting root" messages > the boot process halts without starting INIT. I believe that is because I > am using the old root-2 disk image plus some older RPMS for a boot disk; > am I correct in assuming that I need to update the root image for use with > newer kernels? If so, can I use the RPMS from > intel.cleveland.lug.net:/pub/Mipsel/RPMS (compiled for the Cobalt Qube) or > must I use the RPMS for DECStations? These RPMS should work just fine. Could you try to press the magic hotkeys + and + and mail me the printout if that still works? > Once I get a working userland I will try to find the source for the Linux > framebuffer X-server and see if it compiles on MIPS (or has this already > been accomplished?). Between FB compatibility on the G364 provided by > Thomas and the standard PS/2 mouse on the Magnum I hope to have X running > smoothly soon. The X stuff from the M700 should work just fine - after all the M700 is just a Magnum clone. Ralf From tsbogend@alpha.franken.de Sun Mar 28 23:49:34 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA27932; Sun, 28 Mar 1999 23:49:33 +0200 (MET DST) Received-Date: Sun, 28 Mar 1999 23:49:33 +0200 (MET DST) Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id XAA12865; Sun, 28 Mar 1999 23:49:31 +0200 (MET DST) Received: (from tsbogend@localhost) by alpha.franken.de (8.8.7/8.8.5) id XAA01844 for linux-mips@fnet.fr; Sun, 28 Mar 1999 23:46:04 +0200 Message-ID: <19990328234604.B1792@alpha.franken.de> Date: Sun, 28 Mar 1999 23:46:04 +0200 From: Thomas Bogendoerfer To: linux-mips@fnet.fr Subject: Re: MIPS Magnum update References: <19990324005534.B3168@alpha.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Ryan Rafferty on Sun, Mar 28, 1999 at 01:30:29PM -0500 Content-Length: 1536 Lines: 34 On Sun, Mar 28, 1999 at 01:30:29PM -0500, Ryan Rafferty wrote: > However, after the "freeing unused memory" and "mounting root" messages > the boot process halts without starting INIT. I believe that is because I > am using the old root-2 disk image plus some older RPMS for a boot disk; possible. > am I correct in assuming that I need to update the root image for use with > newer kernels? If so, can I use the RPMS from > intel.cleveland.lug.net:/pub/Mipsel/RPMS (compiled for the Cobalt Qube) or > must I use the RPMS for DECStations? the Qube RPMs should work, but there are also a bunch of RPMs, which I've built on my M700. You can find them on ftp://ftp.linux.sgi.com/pub/linux/mips/mipsel-linux/RPMS > Once I get a working userland I will try to find the source for the Linux > framebuffer X-server and see if it compiles on MIPS (or has this already > been accomplished?). Between FB compatibility on the G364 provided by > Thomas and the standard PS/2 mouse on the Magnum I hope to have X running > smoothly soon. just get the RPMs for X, install it, and run X on your Magnum. No need to compile it yourself:-) But there is still a small bug either in the kernel code or in the X server. It corrupts the screen, when scrolling down (virtual screen), but every 8 lines everything is fine. Thomas. -- This device has completely bogus header. Compaq scores again :-| It's a host bridge, but it should be called ghost bridge instead ;^) [Martin `MJ' Mares on linux-kernel] From mkovach@alpha.theshagster.com Mon Mar 29 14:33:06 1999 Received: from alpha.theshagster.com (mkovach@[207.166.196.19]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA09585; Mon, 29 Mar 1999 14:33:04 +0200 (MET DST) Received-Date: Mon, 29 Mar 1999 14:33:04 +0200 (MET DST) Received: (from mkovach@localhost) by alpha.theshagster.com (8.8.7/8.8.7) id CAA14397 for linux-mips@fnet.fr; Fri, 29 Mar 2019 02:41:19 -0500 Message-ID: <20190329024118.A14388@mkovach.nacs.net> Date: Fri, 29 Mar 1999 02:41:18 -0500 From: Mat Kovach To: linux-mips@fnet.fr Subject: Re: MIPS Magnum update References: <19990324005534.B3168@alpha.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Ryan Rafferty on Sun, Mar 28, 1999 at 01:30:29PM -0500 Content-Length: 952 Lines: 18 On Sun, Mar 28, 1999 at 01:30:29PM -0500, Ryan Rafferty wrote: : : However, after the "freeing unused memory" and "mounting root" messages : the boot process halts without starting INIT. I believe that is because I : am using the old root-2 disk image plus some older RPMS for a boot disk; : am I correct in assuming that I need to update the root image for use with : newer kernels? If so, can I use the RPMS from : intel.cleveland.lug.net:/pub/Mipsel/RPMS (compiled for the Cobalt Qube) or : must I use the RPMS for DECStations? The RPMS on intel.cleveland.lug.net should work in your case. If any of them don't please lets us, at the cleveland linux users group, know. Although they are built on the MIPS arch, we certainly want to make them work on as many differnt mibsel archs as possible. -- Mat Kovach mkovach@mkovach.nacs.net This e-mail is brought to you by the letter gamma and number e From Harald.Koerfgen@home.ivm.de Mon Mar 29 17:58:04 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA10893; Mon, 29 Mar 1999 17:58:00 +0200 (MET DST) Received-Date: Mon, 29 Mar 1999 17:58:00 +0200 (MET DST) Received: from franz.no.dom (port22.koeln.ivm.de [195.247.239.22]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id RAA07441 for ; Mon, 29 Mar 1999 17:57:50 +0200 X-To: Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903281945.MAA22821@harmony.village.org> Date: Mon, 29 Mar 1999 18:00:50 +0200 (MEST) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: linux-mips@fnet.fr Subject: Re: DECstation bootloader Content-Length: 1361 Lines: 37 Hi, On 28-Mar-99 Warner Losh wrote: > In message Harald > Koerfgen writes: >: Well, I don't like this too. On the other hand, I don't see any benefit >: from writing bootblocks or a two stage boot process when the PROM is >: able >: to handle this nicely for us. > > You might want to look into the new bootblocks that were just > committed to the NetBSD tree. They are quite powerful. You will > likely not be able to get the PROMs to do everything you want on the > DECstations. The NetBSD folks have been dealing with the boot problem > for literally years and likely have an excellent grasp on all the > subtle issues involve. > > No slight intened against the people working on this, but I really > hate to see the wheel reinvented yet again :-(. I hate this as well but there are technical reasons to do so, I'm afraid :-(. AFAIK ext2, unlike ufs and ffs, doesn't reserve space for a bootloader except block 0 of a partition. I hope I am wrong here, but I haven't found anything in that direction. That means that a two stage boot process, like Ultrix and NetBSD do it, is a no go if you want to have an ext2 filesystem as the first partition on a disk. Maybe I am making the wrong assumptions here and I'd appreciate if someone with more knowledge of ext2 can correct me. --- Regards, Harald From K.H.C.vanHouten@research.kpn.com Mon Mar 29 19:03:01 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA12066; Mon, 29 Mar 1999 19:03:00 +0200 (MET DST) Received-Date: Mon, 29 Mar 1999 19:03:00 +0200 (MET DST) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J9EVS1FXDQ000049@research.kpn.com> for linux-mips@fnet.fr; Mon, 29 Mar 1999 19:02:58 +0200 Received: by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id TAA13357; Mon, 29 Mar 1999 19:02:52 +0200 X-URL: http://www-lsdm.research.kpn.com/~karel Date: Mon, 29 Mar 1999 19:02:52 +0200 (MET DST) From: K.H.C.vanHouten@research.kpn.com (Karel van Houten) Subject: Re: DECstation bootloader In-reply-to: To: linux-mips@fnet.fr Cc: K.H.C.vanHouten@research.kpn.com (Houten K.H.C. van ) Message-id: <199903291702.TAA13357@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-Length: 1192 Lines: 32 Harald Koerfgen wrote: > > I hate this as well but there are technical reasons to do so, I'm afraid > :-(. > > AFAIK ext2, unlike ufs and ffs, doesn't reserve space for a bootloader > except block 0 of a partition. I hope I am wrong here, but I haven't found > anything in that direction. > > That means that a two stage boot process, like Ultrix and NetBSD do it, is > a no go if you want to have an ext2 filesystem as the first partition on > a disk. > > Maybe I am making the wrong assumptions here and I'd appreciate if someone > with more knowledge of ext2 can correct me. I don't know more about ext2fs, but I think an approach like silo for sparclinux should be possible. My ideas are as follows: - Use MSDOS partition table, that only uses 66 bytes at the end of the first sector. - Port the second stage loader of silo to DECStation linux. - Use (a modified version of) Harald's bootprep to install a map table to load the second stage loader. - I've already modified bootprep.c in such a way that it leaves my partition table in place, and can install 52 maps (instead of 61). As an alternative, I'm trying to compile the netbsd loaders under linux. Regards, Karel. From Harald.Koerfgen@home.ivm.de Mon Mar 29 20:43:16 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id UAA13518; Mon, 29 Mar 1999 20:43:14 +0200 (MET DST) Received-Date: Mon, 29 Mar 1999 20:43:14 +0200 (MET DST) Received: from franz.no.dom (port15.koeln.ivm.de [195.247.239.15]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id UAA17573 for ; Mon, 29 Mar 1999 20:43:02 +0200 X-To: Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903291702.TAA13357@sparta.research.kpn.com> Date: Mon, 29 Mar 1999 20:46:03 +0200 (MEST) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: linux-mips@fnet.fr Subject: Re: DECstation bootloader Content-Length: 1729 Lines: 47 Hi, On 29-Mar-99 Karel van Houten wrote: > Harald Koerfgen wrote: >> AFAIK ext2, unlike ufs and ffs, doesn't reserve space for a bootloader >> except block 0 of a partition. I hope I am wrong here, but I haven't >> found >> anything in that direction. >> >> That means that a two stage boot process, like Ultrix and NetBSD do it, >> is >> a no go if you want to have an ext2 filesystem as the first partition >> on >> a disk. >> >> Maybe I am making the wrong assumptions here and I'd appreciate if >> someone >> with more knowledge of ext2 can correct me. > > I don't know more about ext2fs, but I think an approach like silo for > sparclinux should be possible. > > My ideas are as follows: > - Use MSDOS partition table, that only uses 66 bytes at the end of the > first sector. > - Port the second stage loader of silo to DECStation linux. > - Use (a modified version of) Harald's bootprep to install a map table > to load the second stage loader. > - I've already modified bootprep.c in such a way that it leaves my > partition table in place, and can install 52 maps (instead of 61). That's *exactly* what I had in mind, except using sun partition tables. Well, a part of, just enough that the kernel will recognise them without modification. fdisk has to be modified anyway and my proposal limits the maps to 51 but allows eight partitions instead of four. We simply have to decide what we want. > As an alternative, I'm trying to compile the netbsd loaders under linux. If I understand things correctly, I haven't looked into the source yet, the second stage loader may fit our needs, but I don't know if it understands ext2. silo's second stage *might* be less work. Happy hacking. --- Regards, Harald From imp@harmony.village.org Mon Mar 29 21:11:45 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA14243; Mon, 29 Mar 1999 21:11:41 +0200 (MET DST) Received-Date: Mon, 29 Mar 1999 21:11:41 +0200 (MET DST) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id TAA05215 for ; Mon, 29 Mar 1999 19:11:34 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA02998 for ; Mon, 29 Mar 1999 12:10:59 -0700 (MST) Message-Id: <199903291910.MAA02998@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: DECstation bootloader In-reply-to: Your message of "Mon, 29 Mar 1999 18:00:50 +0200." References: Date: Mon, 29 Mar 1999 12:10:59 -0700 From: Warner Losh Content-Length: 1963 Lines: 43 In message Harald Koerfgen writes: : AFAIK ext2, unlike ufs and ffs, doesn't reserve space for a bootloader : except block 0 of a partition. I hope I am wrong here, but I haven't found : anything in that direction. Doesn't matter one way or the other. Given that ext2fs is just ufs with some hacks (from a file sytstem point of view), I'd be extremely surprised if it doesn't. Looking at the FreeBSD implementation I see that it has 1024 bytes reserved at the front of the file system. That's two blocks :-). Even if I'm wrong, this is a simple matter for disklabel. Just don't allow a partition to start at 0. If you do, you can't boot off of it. Make sure the label is in the first 1024 bytes and you are set. It looks like ext2fs reserves 1k for all file systems (just like ufs/ffs (they are the same thing) reserve 8k at the start of the file system). Looks like there are some other games that you can play. You can reserve the first 9k of those partitions that start at block 0. Then you can put the first stage into the first 1k, then you can put the second stage into 2k-8.5k. It looks like ext2fs supports s_first_data_block could be used to reserve this area. Or maybe the s_r_blocks_count. To be honest, I didn't look in more detail to see if setting these would work. Also, there are 235*4 ( = 940 bytes) free in the superblock as well, but that might be pushing your luck... Hmmm, a little more digging shows that neither of those two fields are used to offset the group descriptors, which start at super block plus 1. I still think it would be easier to move the offset of the 'a' partition from '0' to '16', which would solve this problem. If the disk label was in the first 1024 bytes of the sector, then you could still use the 'c' partition on other disks. After all, many of the free oses start their first partition at 16 to avoid boot manager crap in the PC world. Warner From tor@spacetec.no Mon Mar 29 21:27:13 1999 Received: from pallas.spacetec.no (pallas.spacetec.no [192.51.5.92]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA14458; Mon, 29 Mar 1999 21:27:12 +0200 (MET DST) Received-Date: Mon, 29 Mar 1999 21:27:12 +0200 (MET DST) Received: (from tor@localhost) by pallas.spacetec.no (8.9.1a/8.9.1) id VAA25202 for linux-mips@fnet.fr; Mon, 29 Mar 1999 21:26:46 +0200 Message-Id: <199903291926.VAA25202@pallas.spacetec.no> From: tor@spacetec.no (Tor Arntsen) Date: Mon, 29 Mar 1999 21:26:44 +0200 In-Reply-To: Warner Losh "Re: DECstation bootloader" (Mar 29, 20:16) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: linux-mips@fnet.fr Subject: Re: DECstation bootloader Content-Length: 664 Lines: 15 Just to add to the many descriptions: On SGI, if you want to be able to boot from a disk, you are not allowed to put a partition for an ordinary file system (EFS or XFS) at 0. Instead you make a special partition starting at 0 which they call Volume Header (as far as I can tell this is still just a partition as any other). It's just a small partition where they store the 'sash' second stage boot loader, and whatever other stand-alone tools you would want there, like system testers, fx (disk partitioner) etc. You can make the partition as big as you want, usually it's one or two megabytes. They use a special program to copy files to/from there. - Tor From kurt_kayser@hotmail.com Tue Mar 30 00:45:17 1999 Received: from planning.viaginterkom.de (planning.viaginterkom.de [62.180.7.29]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA19351; Tue, 30 Mar 1999 00:45:17 +0200 (MET DST) Received-Date: Tue, 30 Mar 1999 00:45:17 +0200 (MET DST) Received: from hotmail.com (u-153.munchen.ipdial.viaginterkom.de [62.180.7.153]) by planning.viaginterkom.de (8.8.8/8.8.8-Antispam) with ESMTP id AAA20854 for ; Tue, 30 Mar 1999 00:44:10 +0200 (MET DST) Message-ID: <37000297.878A9BE5@hotmail.com> Date: Tue, 30 Mar 1999 00:45:43 +0200 From: Kurt Kayser Organization: Araponga Inc. X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: PDA-MIPS port? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 330 Lines: 13 Hello! I wonder, if anybody thought of porting Linux to the MIPS processor type that is used in some PDA hardware. Currently I can only find WinCE software that is available, and 'somewhat' limited in its flexibility. :-) I would greatly appreciate any hints where people are discussion this topic in more depth. Thanks, Kurt From bjorn.ramqvist@notes.sema.se Tue Mar 30 08:44:39 1999 Received: from cassini.sto.sema.se (cassini.sto.sema.se [195.17.98.36]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id IAA26728; Tue, 30 Mar 1999 08:44:39 +0200 (MET DST) Received-Date: Tue, 30 Mar 1999 08:44:39 +0200 (MET DST) From: bjorn.ramqvist@notes.sema.se Received: from sundsvall3.notes.sema.se (notes.sema.se [172.22.12.23]) by cassini.sto.sema.se (8.8.7/8.8.7) with SMTP id IAA08805 for ; Tue, 30 Mar 1999 08:44:06 +0200 Received: by sundsvall3.notes.sema.se(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999)) id 41256744.002521EB ; Tue, 30 Mar 1999 07:45:35 +0100 X-Lotus-FromDomain: SEMA_GROUP To: linux-mips@fnet.fr Message-ID: <41256744.002521D4.00@sundsvall3.notes.sema.se> Date: Tue, 30 Mar 1999 09:45:57 +0200 Subject: Re: DECstation bootloader Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=kY6719kgebJMvlur3OQc1E2nKa0ixQXUQ89wBlDVZBmO8BbYMiQpaPw8" Content-Disposition: inline Content-Length: 1252 Lines: 59 --0__=kY6719kgebJMvlur3OQc1E2nKa0ixQXUQ89wBlDVZBmO8BbYMiQpaPw8 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable I don't know how different the VAX-architectures bootproms are from the= DECstations, but Linux/VAX already has a bootloader running (If I haven't got all this = wrong). Check out http://www.mssl.ucl.ac.uk/~atp/linux-vax/ Perhaps we could get some ideas from him? (Linux/VAX is also a very interesting port, IMHO.) :-) /Regards, Bjorn K.H.C.vanHouten@research.kpn.com (Karel van Houten) on 99-03-29 18:02:5= 2 Please respond to linux-mips@fnet.fr To: linux-mips@fnet.fr cc: K.H.C.vanHouten@research.kpn.com (Houten K.H.C. van ) (bcc: Bj=F6= rn Ramqvist/OER/Sema Group/SE) Subject: Re: DECstation bootloader = --0__=kY6719kgebJMvlur3OQc1E2nKa0ixQXUQ89wBlDVZBmO8BbYMiQpaPw8 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Harald Koerfgen wrote: I don't know more about ext2fs, but I think an approach like silo for sparclinux should be possible. As an alternative, I'm trying to compile the netbsd loaders under linux. Regards, Karel. --0__=kY6719kgebJMvlur3OQc1E2nKa0ixQXUQ89wBlDVZBmO8BbYMiQpaPw8-- From imp@harmony.village.org Tue Mar 30 11:11:32 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA29277; Tue, 30 Mar 1999 11:10:49 +0200 (MET DST) Received-Date: Tue, 30 Mar 1999 11:10:49 +0200 (MET DST) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id JAA08833 for ; Tue, 30 Mar 1999 09:10:19 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA01624 for ; Tue, 30 Mar 1999 02:10:14 -0700 (MST) Message-Id: <199903300910.CAA01624@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: PDA-MIPS port? In-reply-to: Your message of "Tue, 30 Mar 1999 00:45:43 +0200." <37000297.878A9BE5@hotmail.com> References: <37000297.878A9BE5@hotmail.com> Date: Tue, 30 Mar 1999 02:10:14 -0700 From: Warner Losh Content-Length: 1195 Lines: 25 In message <37000297.878A9BE5@hotmail.com> Kurt Kayser writes: : I wonder, if anybody thought of porting Linux to the MIPS processor : type that is used in some PDA hardware. Currently I can only find : WinCE software that is available, and 'somewhat' limited in its : flexibility. :-) This has come up several times on this list. There is a relatively private effort underway by some Japanese hackers to put NetBSD on a NEC Mobile Gear 2 (a japanese only, MIPS Vr4111 or Vr4121 based PDA). They have a working boot loader which loads NetBSD to a certain point. Since I don't have any working PDAs right now (I won a Everex E-10 on Ebay and am awaiting delivery), I've not tried it, but have built the NetBSD kernel. I've also added a serial driver for the odd-ball debug serial port that the Vr4111 has. I was corresponding with someone who was working on a Linux port, but I haven't heard much from him lately. I outlined how to write a boot loader, and he wrote one, but I don't know how well it is working. At this point, I'm tossing my hat in the NetBSD ring for this project and will be unlikely to do Linux work in this area unless someone gives me a contract to do that. Warner From Harald.Koerfgen@home.ivm.de Tue Mar 30 19:42:43 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA03422; Tue, 30 Mar 1999 19:42:41 +0200 (MET DST) Received-Date: Tue, 30 Mar 1999 19:42:41 +0200 (MET DST) Received: from franz.no.dom (port33.koeln.ivm.de [195.247.239.33]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id TAA08126 for ; Tue, 30 Mar 1999 19:42:30 +0200 X-To: Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903291926.VAA25202@pallas.spacetec.no> Date: Tue, 30 Mar 1999 18:45:08 +0200 (MEST) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: linux-mips@fnet.fr Subject: Re: DECstation bootloader Content-Length: 1039 Lines: 27 Hi, On 29-Mar-99 Tor Arntsen wrote: > Just to add to the many descriptions: > On SGI, if you want to be able to boot from a disk, you are not allowed > to put a partition for an ordinary file system (EFS or XFS) at 0. > Instead you make a special partition starting at 0 which they call > Volume Header (as far as I can tell this is still just a partition as > any other). > > It's just a small partition where they store the 'sash' second stage > boot > loader, and whatever other stand-alone tools you would want there, like > system testers, fx (disk partitioner) etc. > > You can make the partition as big as you want, usually it's one or two > megabytes. They use a special program to copy files to/from there. Not bad idea. We could make a small ffs partition as the first one, put the kernel on it and boot with the NetBSD bootloader at zero cost. Karel, I assume you have the new NetBSD bootblocks already on your box. Could you please check wether it's possible to boot an elf linux kernel with these? --- Regards, Harald From akonstantinov@yahoo.com Tue Mar 30 20:48:29 1999 Received: from web135.yahoomail.com (web135.yahoomail.com [205.180.60.20]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id UAA04226; Tue, 30 Mar 1999 20:48:28 +0200 (MET DST) Received-Date: Tue, 30 Mar 1999 20:48:28 +0200 (MET DST) Message-ID: <19990330184834.8684.rocketmail@web135.yahoomail.com> Received: from [205.180.60.12] by web135.yahoomail.com; Tue, 30 Mar 1999 10:48:34 PST Date: Tue, 30 Mar 1999 10:48:34 -0800 (PST) From: Aleksandr Konstantinov Subject: Re: linux om RM200 To: linux-mips@fnet.fr MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Length: 904 Lines: 37 --- Wiebe Wiersema wrote: > L.s. > > I have a Siemens Nixdorf RM200. I am trying to get > the stuff booted with > milo and the dummy vmlinux. > > But first I seem to need the NT firmware loaded in my > RM200 boot memory, > could you refer me to the guys who had their RM200 up > and running with > linux ? I have 3 friends/colleagues who have a RM200 > as well and would > love to have Linux running on their boxes. (We got > the RM200's as they > were replaced by windoze NT machines damn damn, but > they will suit our > purposes if we get linux up and running to a certain > degree 8-) > > Thanks in advance, > > > Wiebe Wiersema > If Your RM200 has ISA bus (very old one) and You still want that firmware, I can mail it ti You. A.K. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com From spetey@umich.edu Tue Mar 30 21:17:24 1999 Received: from gremlins.rs.itd.umich.edu (gremlins.rs.itd.umich.edu [141.211.83.13]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA05030; Tue, 30 Mar 1999 21:17:17 +0200 (MET DST) Received-Date: Tue, 30 Mar 1999 21:17:17 +0200 (MET DST) Received: from umich.edu ([141.211.55.110]) by gremlins.rs.itd.umich.edu (8.8.8/2.5) with ESMTP id OAA29994; Tue, 30 Mar 1999 14:17:13 -0500 (EST) Message-ID: <37012352.65B342C3@umich.edu> Date: Tue, 30 Mar 1999 14:17:39 -0500 From: Stephen Petersen X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: linux-mips@fnet.fr Subject: Linux for NEC's MobilePro Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 364 Lines: 11 Hi, I know very little about programming (a little java and c++, and basic) but I wonder if it's possible to talk to my NEC MobilePro (a MIPS R4000 handheld with WinCE in ROM) from a Linux machine. I'd just like to be able to swap files through the serial port. How can I find such software... or learn to write it myself? Thanks for your time, Steve Petersen From imp@harmony.village.org Tue Mar 30 21:48:57 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA06174; Tue, 30 Mar 1999 21:48:55 +0200 (MET DST) Received-Date: Tue, 30 Mar 1999 21:48:55 +0200 (MET DST) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id TAA10470 for ; Tue, 30 Mar 1999 19:48:51 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA03987 for ; Tue, 30 Mar 1999 12:48:56 -0700 (MST) Message-Id: <199903301948.MAA03987@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: Linux for NEC's MobilePro In-reply-to: Your message of "Tue, 30 Mar 1999 14:17:39 EST." <37012352.65B342C3@umich.edu> References: <37012352.65B342C3@umich.edu> Date: Tue, 30 Mar 1999 12:48:56 -0700 From: Warner Losh Content-Length: 421 Lines: 11 In message <37012352.65B342C3@umich.edu> Stephen Petersen writes: : I know very little about programming (a little java and c++, and basic) : but I wonder if it's possible to talk to my NEC MobilePro (a MIPS R4000 : handheld with WinCE in ROM) from a Linux machine. I'd just like to be : able to swap files through the serial port. : : How can I find such software... or learn to write it myself? You are SOL. Warner From tsbogend@alpha.franken.de Wed Mar 31 01:21:53 1999 Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA10192; Wed, 31 Mar 1999 01:21:52 +0200 (MET DST) Received-Date: Wed, 31 Mar 1999 01:21:52 +0200 (MET DST) Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/990126/louis-blanc); id BAA09916; Wed, 31 Mar 1999 01:21:50 +0200 (MET DST) Received: (from tsbogend@localhost) by alpha.franken.de (8.8.7/8.8.5) id AAA03876 for linux-mips@fnet.fr; Wed, 31 Mar 1999 00:24:52 +0200 Message-ID: <19990331002451.F2991@alpha.franken.de> Date: Wed, 31 Mar 1999 00:24:51 +0200 From: Thomas Bogendoerfer To: linux-mips@fnet.fr Subject: Re: DECstation bootloader References: <199903291926.VAA25202@pallas.spacetec.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: ; from Harald Koerfgen on Tue, Mar 30, 1999 at 06:45:08PM +0200 Content-Length: 988 Lines: 22 On Tue, Mar 30, 1999 at 06:45:08PM +0200, Harald Koerfgen wrote: > Not bad idea. We could make a small ffs partition as the first one, put the > kernel on it and boot with the NetBSD bootloader at zero cost. but keep in mind, that the Linux UFS filesystem code isn't ready for prime time (at least the write support). > Karel, I assume you have the new NetBSD bootblocks already on your box. > Could you please check wether it's possible to boot an elf linux kernel > with these? I doubt it, but it may already boot ECOFF kernels. And even if this doesn't work, you should be able to use the ELF loading stuff, I've added to a NetBSD bootloader derivate for my Sun 3/80. I'm also looking into adding ext2fs support to it, but this has to wait at the moment. Thomas. -- This device has completely bogus header. Compaq scores again :-| It's a host bridge, but it should be called ghost bridge instead ;^) [Martin `MJ' Mares on linux-kernel] From imp@harmony.village.org Wed Mar 31 03:06:23 1999 Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id DAA12172; Wed, 31 Mar 1999 03:06:21 +0200 (MET DST) Received-Date: Wed, 31 Mar 1999 03:06:21 +0200 (MET DST) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id BAA11333 for ; Wed, 31 Mar 1999 01:06:16 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA05667 for ; Tue, 30 Mar 1999 18:06:23 -0700 (MST) Message-Id: <199903310106.SAA05667@harmony.village.org> To: linux-mips@fnet.fr Subject: Re: DECstation bootloader In-reply-to: Your message of "Wed, 31 Mar 1999 00:24:51 +0200." <19990331002451.F2991@alpha.franken.de> References: <19990331002451.F2991@alpha.franken.de> <199903291926.VAA25202@pallas.spacetec.no> Date: Tue, 30 Mar 1999 18:06:23 -0700 From: Warner Losh Content-Length: 460 Lines: 10 In message <19990331002451.F2991@alpha.franken.de> Thomas Bogendoerfer writes: : I doubt it, but it may already boot ECOFF kernels. And even if this doesn't : work, you should be able to use the ELF loading stuff, I've added to : a NetBSD bootloader derivate for my Sun 3/80. I'm also looking into adding : ext2fs support to it, but this has to wait at the moment. NetBSD/pmax's boot blocks will boot ELF, ECOFF and a.out kernels from ufs partitions. Warner From K.H.C.vanHouten@research.kpn.com Wed Mar 31 09:33:15 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id JAA16022; Wed, 31 Mar 1999 09:33:14 +0200 (MET DST) Received-Date: Wed, 31 Mar 1999 09:33:14 +0200 (MET DST) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J9H4HDF04S0000JC@research.kpn.com> for linux-mips@fnet.fr; Wed, 31 Mar 1999 09:33:11 +0200 Received: from sparta.research.kpn.com by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id JAA10156; Wed, 31 Mar 1999 09:33:10 +0200 Date: Wed, 31 Mar 1999 09:33:09 +0200 From: "Houten K.H.C. van (Karel)" Subject: Re: DECstation bootloader In-reply-to: "Your message of Tue, 30 Mar 1999 18:06:23 PDT." <199903310106.SAA05667@harmony.village.org> To: linux-mips@fnet.fr Cc: K.H.C.vanHouten@research.kpn.com Reply-to: K.H.C.vanHouten@research.kpn.com Message-id: <199903310733.JAA10156@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: exmh version 1.6.5 12/11/95 Content-type: text/plain; charset=us-ascii X-Face: ";:TzQQC{mTp~$W,'m4@Lu1Lu$rtG_~5kvYO~F:C'KExk9o1X"iRz[0%{bq?6Aj#>VhSD?v 1W9`.Qsf+P&*iQEL8&y,RDj&U.]!(R-?c-h5h%Iw%r$|%6+Jc>GTJe!_1&A0o'lC[`I#={2BzOXT1P q366I$WL=;[+SDo1RoIT+a}_y68Y:jQ^xp4=*4-ryiymi>hy Content-Length: 853 Lines: 28 Warner Losh wrote: > In message <19990331002451.F2991@alpha.franken.de> Thomas Bogendoerfer writes: > : I doubt it, but it may already boot ECOFF kernels. And even if this doesn't > : work, you should be able to use the ELF loading stuff, I've added to > : a NetBSD bootloader derivate for my Sun 3/80. I'm also looking into adding > : ext2fs support to it, but this has to wait at the moment. > > NetBSD/pmax's boot blocks will boot ELF, ECOFF and a.out kernels from > ufs partitions. > > Warner > I tried the ELF kernel, and it did start the (linux) loader, but did NOT start the kernel itself. -- Karel van Houten ---------------------------------------------------------- The box said "Requires Windows 95 or better." I can't understand why it won't work on my Linux computer. ---------------------------------------------------------- From Harald.Koerfgen@home.ivm.de Wed Mar 31 17:40:39 1999 Received: from aw.ivm.net (mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA21320; Wed, 31 Mar 1999 17:40:37 +0200 (MET DST) Received-Date: Wed, 31 Mar 1999 17:40:37 +0200 (MET DST) Received: from franz.no.dom (port29.koeln.ivm.de [195.247.239.29]) by aw.ivm.net (8.8.8/8.8.8) with ESMTP id RAA20379; Wed, 31 Mar 1999 17:40:25 +0200 X-To: linux-mips@fnet.fr Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903310733.JAA10156@sparta.research.kpn.com> Date: Wed, 31 Mar 1999 16:43:03 +0200 (MEST) Reply-To: "Harald Koerfgen" Organization: none Sender: harry@franz.no.dom From: Harald Koerfgen To: linux-mips@fnet.fr Subject: Re: DECstation bootloader Cc: K.H.C.vanHouten@research.kpn.com Content-Length: 695 Lines: 23 On 31-Mar-99 Houten K.H.C. van (Karel) wrote: > Warner Losh wrote: > >> NetBSD/pmax's boot blocks will boot ELF, ECOFF and a.out kernels from >> ufs partitions. > > I tried the ELF kernel, and it did start the (linux) loader, but did NOT > start the kernel itself. Does that mean you're seeing a "This DECstation is a 5000/2x0" message and then nothing? If so, we're in excellent shape. That simply means that the NetBSD bootloader passes the command line parameters in a different way than the PROM. Please change "#undef PROM_DEBUG" to "#define PROM_DEBUG" in arch/mips/dec/prom/cmdline.c, look what happens and change "prom_init_cmdline" accordingly. Happy hacking. --- Regards, Harald From K.H.C.vanHouten@research.kpn.com Wed Mar 31 17:55:29 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA21873; Wed, 31 Mar 1999 17:55:27 +0200 (MET DST) Received-Date: Wed, 31 Mar 1999 17:55:27 +0200 (MET DST) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J9HM0SR43C0000KJ@research.kpn.com> for linux-mips@fnet.fr; Wed, 31 Mar 1999 17:55:23 +0200 Received: by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id RAA29125; Wed, 31 Mar 1999 17:55:12 +0200 X-URL: http://www-lsdm.research.kpn.com/~karel Date: Wed, 31 Mar 1999 17:55:12 +0200 (MET DST) From: K.H.C.vanHouten@research.kpn.com (Karel van Houten) Subject: Re: DECstation bootloader In-reply-to: To: Harald.Koerfgen@home.ivm.de Cc: linux-mips@fnet.fr, K.H.C.vanHouten@research.kpn.com Message-id: <199903311555.RAA29125@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-Length: 2581 Lines: 75 Hi Harald, You wrote: > Does that mean you're seeing a "This DECstation is a 5000/2x0" message and > then nothing? > > If so, we're in excellent shape. That simply means that the NetBSD > bootloader passes the command line parameters in a different way than the > PROM. Please change "#undef PROM_DEBUG" to "#define PROM_DEBUG" in > arch/mips/dec/prom/cmdline.c, look what happens and change > "prom_init_cmdline" accordingly. Here the result without the above suggestion. I'll now try your suggestion. KN05 V2.1k >>boot 3/rz3/vmlinux >> NetBSD/pmax Secondary Boot, Revision 1.0 >> (simonb@mona, Fri Mar 26 14:48:06 EST 1999) Boot: 3/rz3/vmlinux 1169552+122480/[190+94448+89966]=0x168b74 Starting at 0x800405cc This DECstation is a DS5000/2x0 [Now nothing, I have to press the reset button] ??? ? PC: 0xa013faac ? CR: 0x0000001c ? SR: 0x30510006 ? CFG: 0x10410483 ? ? MB_CS: 0x00bf8001 ? MB_INT: 0x101f0000 <> ? ? SIR: 0x00088001 ? SIRM: 0x00000000 ? ? at:30010000 a2:0000F000 t3:30010000 s0:10410483 s5:00000003 k1:FF7FFAFF ? v0:80058D94 a3:00001000 t4:801359E0 s1:A000FD79 s6:00000000 gp:80046000 ? v1:80170000 t0:00000000 t5:00000020 s2:A000FCF0 s7:DFFDBAFF sp:80047FA0 ? a0:10410483 t1:FFFF00FF t6:BF980000 s3:00000001 t8:0000000A fp:F5C759FA ? a1:00000001 t2:0000003C t7:00000004 s4:00000000 t9:A0004C70 ra:A014061C KN05 V2.1k (PC: 0xa013faac, SP: 0x80047fa0) 3/prcache >>boot -tftp boot(3), bootp|139.63.1.4:/tftpboot/nbImage/ -tftp load 1169824+113264+122480 Launching kernel... This DECstation is a DS5000/2x0 Loading R4000 MMU routines. CPU revision is: 00000440 .... .... Partition check: sda: sda1 sda2 (MSDOS partition table) sdb: sdb1 sdb2 sdb3 sdb4 sdb5 (NETBSD partition table, LE, offset 64) sdc: sdc1 sdc2 sdc3 sdc4 sdc5 (NETBSD partition table, LE, offset 64) VFS: Mounted root (ext2 filesystem) readonly. .... .... [root@elrond /root]# mount -t ufs -o ro,ufstype=44bsd /dev/sdc1 /netbsd [root@elrond /root]# cd /netbsd [root@elrond /netbsd]# ls -llvmlinux -rwxr-xr-x 1 root root 1818114 Mar 27 13:39 vmlinux [root@elrond /netbsd]# file vmlinux vmlinux: ELF 32-bit LSB executable, MIPS R3000_BE - invalid byte order, version 1, statically linked, not stripped [root@elrond /netbsd]# Note that when booting from the netbsd bootblock, I don't get "Launching kernel...", but directly "This DECstation is a DS5000/2x0" I'll keep you informed. From K.H.C.vanHouten@research.kpn.com Wed Mar 31 18:57:18 1999 Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA23048; Wed, 31 Mar 1999 18:57:17 +0200 (MET DST) Received-Date: Wed, 31 Mar 1999 18:57:17 +0200 (MET DST) Received: from sparta.research.kpn.com by research.kpn.com (PMDF V5.1-12 #D3519) with SMTP id <01J9HO6HRJU60000V5@research.kpn.com> for linux-mips@fnet.fr; Wed, 31 Mar 1999 18:57:09 +0200 Received: by sparta.research.kpn.com (SMI-8.6/SMI-SVR4) id SAA00793; Wed, 31 Mar 1999 18:57:03 +0200 X-URL: http://www-lsdm.research.kpn.com/~karel Date: Wed, 31 Mar 1999 18:57:03 +0200 (MET DST) From: K.H.C.vanHouten@research.kpn.com (Karel van Houten) Subject: Re: DECstation bootloader In-reply-to: <199903311555.RAA29125@sparta.research.kpn.com> To: linux-mips@fnet.fr Cc: Harald.Koerfgen@home.ivm.de, K.H.C.vanHouten@research.kpn.com Message-id: <199903311657.SAA00793@sparta.research.kpn.com> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-Length: 832 Lines: 32 And here the results with PROM_DEBUG: KN05 V2.1k (PC: 0xa013faac, SP: 0xffffdeb0) >>boot 3/rz3/vmlinux console=ttyS2 root=/dev/sda1 >> NetBSD/pmax Secondary Boot, Revision 1.0 >> (simonb@mona, Fri Mar 26 14:48:06 EST 1999) Boot: 3/rz3/vmlinux 1169552+122480/[190+94448+89966]=0x168b74 Starting at 0x800405cc This DECstation is a DS5000/2x0 arcs_cmdline: root=/dev/sda1 KN05 V2.1k (PC: 0xa013faac, SP: 0x80047f68) >>boot 3/rz3/vmlinux -- console=ttyS2 root=/dev/sda1 >> NetBSD/pmax Secondary Boot, Revision 1.0 >> (simonb@mona, Fri Mar 26 14:48:06 EST 1999) Boot: 3/rz3/vmlinux 1169552+122480/[190+94448+89966]=0x168b74 Starting at 0x800405cc This DECstation is a DS5000/2x0 arcs_cmdline: console=ttyS2 root=/dev/sda1 KN05 V2.1k (PC: 0xa013faac, SP: 0x80047f68) >> Both times the system auto-resets. Regards, Karel. From garyb@ee.bath.ac.uk Thu Apr 1 11:46:28 1999 Received: from pat.bath.ac.uk (qmailr@pat.bath.ac.uk [138.38.32.2]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id LAA10195; Thu, 1 Apr 1999 11:46:26 +0200 (MET DST) Received-Date: Thu, 1 Apr 1999 11:46:26 +0200 (MET DST) Received: (qmail 20803 invoked from network); 1 Apr 1999 09:46:13 -0000 Received: from albion.bath.ac.uk (138.38.66.204) by pat.bath.ac.uk with SMTP; 1 Apr 1999 09:46:13 -0000 Received: (from mail@localhost) by albion.bath.ac.uk (8.9.0/8.9.0) id KAA00264 for ; Thu, 1 Apr 1999 10:44:32 +0100 X-Authentication-Warning: albion.bath.ac.uk: mail set sender to using -f Received: from eepc-pss5.bath.ac.uk(138.38.67.6) by albion.bath.ac.uk via smap (V2.1) id xma000262; Thu, 1 Apr 99 10:44:17 +0100 Received: from localhost (gary@localhost) by eepc-pss5.bath.ac.uk (8.9.0/8.9.0) with SMTP id UAA32014 for ; Wed, 31 Mar 1999 20:04:04 +0100 Date: Wed, 31 Mar 1999 20:04:04 +0100 (GMT) From: Gary Benson To: linux-mips@fnet.fr Subject: Hello Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 568 Lines: 16 Hi, I have just aquired an Indy with a bust hard disk. It has no floppy drives, but it has a cdrom. Any idea what to do to make it work (aside from getting a new hard disk)? I have used Linux on PC's before but I have never seen an SGI before today! Any suggestions? Cheers anyway, Gary ____________________________________________________________________ Gary Benson, Research Officer, 2E1.19, Power & Energy Systems Group, School of Electronic and Electrical Engineering, University of Bath, Claverton Down,Bath,BA2 7AY garyb@ee.bath.ac.uk (44/0)1225 82(6076) From airlied@csn.ul.ie Wed Mar 31 23:37:00 1999 Received: from beast.csn.ul.ie (root@beast.csn.ul.ie [136.201.105.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA28311; Wed, 31 Mar 1999 23:36:57 +0200 (MET DST) Received-Date: Wed, 31 Mar 1999 23:36:57 +0200 (MET DST) Received: from skynet.csn.ul.ie (airlied@skynet.csn.ul.ie [136.201.105.2]) by beast.csn.ul.ie (8.8.8/8.8.8) with ESMTP id XAA29645 for ; Wed, 31 Mar 1999 23:30:33 +0100 Received: from localhost (airlied@localhost) by skynet.csn.ul.ie (8.8.5/8.8.5) with SMTP id WAA06533 for ; Wed, 31 Mar 1999 22:35:23 +0100 Date: Wed, 31 Mar 1999 22:35:22 +0100 (IST) From: Dave Airlie To: linux-mips@fnet.fr Subject: DECstation 5000/200 does it work? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1096 Lines: 24 Hi, I recently downloaded the linux-2.2.1-dec.tar.gz from ftp.linux.sgi.com, and cross-compiled it on my x86 Whether I boot the kernel on a serial console or on the monitor/keyboard I get KN02-AA V5.3c (PC: 0x80061230, SP: 0x80ffbef0) >>boot 6/tftp 1204560+115392+105472 Launching kernel... mips_memory_upper: 0x81000000 This DECstation is a DS5000/200 arcs_cmdline: I've turned on the PROM_DEBUG in the two files that have it, but at this point my system just hangs... any pointers? Dave. ------------ David Airlie, David.Airlie@ul.ie,airlied@skynet -------- Telecommunications Research Centre, ECE Dept, University of Limerick \ http://www.csn.ul.ie/~airlied -- Telecommunications Researcher \ --- TEL: +353-61-202695 -----------------------------------------------