From owner-freebsd-mobile Sun Dec 14 03:10:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA28735 for mobile-outgoing; Sun, 14 Dec 1997 03:10:43 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA28714 for ; Sun, 14 Dec 1997 03:10:34 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id MAA12345 for ; Sun, 14 Dec 1997 12:07:00 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mobile@freebsd.org Subject: 800x600 on laptops (answer to Deng Hongwei) Date: Sun, 14 Dec 1997 12:06:58 +0100 Message-ID: <12343.882097618@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Deng, email to you bounces, see the headers at the bottom of this email!) In message <349308CC.FD11DC6D@sz.cei.go.cn>, Deng Hongwei writes: >So, Would you please tell me howto get the patch and howto set VESA >videomode 0x102 (800x600x16) before loading kernel. the patch is included below. it's still being reviewed and mangled by Soren Schmidt, but eventually it will be included I think. You need to compile a font into your kernel as well, add this to your config file: options "STD8X16FONT" makeoptions "STD8X16FONT"="iso-thin" You give the option "-b" to the kernel when you boot. You can do this automatically by cat > /boot.config -b ^D Please ask if you have questions... Poul-Henning Index: i386/include/console.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/console.h,v retrieving revision 1.33 diff -u -r1.33 console.h - --- console.h 1997/12/07 08:08:49 1.33 +++ console.h 1997/12/07 21:42:35 @@ -150,6 +150,7 @@ #define KD_EGA 4 /* enhanced graphics adapter */ #define KD_VGA 5 /* video graphics adapter */ #define KD_PC98 6 /* PC-98 display */ +#define KD_PIXEL 7 /* pixel/graphics adapter/mode */ #define KD_TEXT 0 /* set text mode restore fonts */ #define KD_TEXT0 0 /* ditto */ Index: i386/isa/syscons.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/syscons.c,v retrieving revision 1.242 diff -u -r1.242 syscons.c - --- syscons.c 1997/12/07 08:09:19 1.242 +++ syscons.c 1997/12/07 21:42:46 @@ -56,6 +56,7 @@ #include #include #include +#include #include #include @@ -92,7 +93,7 @@ #define MODE_PARAM_SIZE 64 /* XXX use sc_bcopy where video memory is concerned */ - -#define sc_bcopy generic_bcopy + extern void generic_bcopy(const void *, void *, size_t); static default_attr user_default = { @@ -136,6 +137,7 @@ u_char scr_map[256]; u_char scr_rmap[256]; char *video_mode_ptr = NULL; +static int vesa_mode; int fonts_loaded = 0 #ifdef STD8X16FONT | FONT_16 @@ -222,13 +224,14 @@ static scr_stat *get_scr_stat(dev_t dev); static scr_stat *alloc_scp(void); static void init_scp(scr_stat *scp); +static void sc_bcopy(u_short *p, int from, int to, int mark); static int get_scr_num(void); static timeout_t scrn_timer; static void stop_scrn_saver(void (*saver)(int)); static void clear_screen(scr_stat *scp); static int switch_scr(scr_stat *scp, u_int next_scr); static void exchange_scr(void); - -static inline void move_crsr(scr_stat *scp, int x, int y); +static void move_crsr(scr_stat *scp, int x, int y); static void scan_esc(scr_stat *scp, u_char c); static void draw_cursor_image(scr_stat *scp); static void remove_cursor_image(scr_stat *scp); @@ -293,12 +296,18 @@ /* * These functions need to be before calls to them so they can be inlined. */ - -static inline void +static void draw_cursor_image(scr_stat *scp) { u_short cursor_image, *ptr = Crtat + (scp->cursor_pos - scp->scr_buf); u_short prev_image; + if (vesa_mode) { + sc_bcopy(scp->scr_buf, scp->cursor_pos - scp->scr_buf, + scp->cursor_pos - scp->scr_buf, 1); + return; + } + /* do we have a destructive cursor ? */ if (flags & CHAR_CURSOR) { prev_image = scp->cursor_saveunder; @@ -324,8 +333,7 @@ cursor_image &= 0xff00; cursor_image |= DEAD_CHAR; } - - } - - else { + } else { cursor_image = (*(ptr) & 0x00ff) | *(scp->cursor_pos) & 0xff00; scp->cursor_saveunder = cursor_image; if (!(flags & BLINK_CURSOR)||((flags & BLINK_CURSOR)&&(blinkrate & 4))){ @@ -343,13 +351,17 @@ *ptr = cursor_image; } - -static inline void +static void remove_cursor_image(scr_stat *scp) { - - *(Crtat + (scp->cursor_oldpos - scp->scr_buf)) = scp->cursor_saveunder; + if (vesa_mode) + sc_bcopy(scp->scr_buf, scp->cursor_oldpos - scp->scr_buf, + scp->cursor_oldpos - scp->scr_buf, 0); + else + *(Crtat + (scp->cursor_oldpos - scp->scr_buf)) = scp->cursor_saveunder; } - -static inline void +static void move_crsr(scr_stat *scp, int x, int y) { if (x < 0) @@ -409,7 +421,12 @@ cp = (u_short *)CGA_BUF; was = *cp; *cp = (u_short) 0xA55A; - - if (*cp == 0xA55A) { + if (bootinfo.bi_vesa == 0x102) { + vesa_mode = bootinfo.bi_vesa; + Crtat = (u_short *)pa_to_va(0xA0000); + crtc_type = KD_PIXEL; + bzero(Crtat, 800*600/8); + } else if (*cp == 0xA55A) { Crtat = (u_short *)CGA_BUF; crtc_addr = COLOR_BASE; crtc_type = KD_CGA; @@ -425,45 +442,43 @@ } *cp = was; - - /* - - * Check rtc and BIOS date area. - - * XXX: don't use BIOSDATA_EQUIPMENT, it is not a dead copy - - * of RTC_EQUIPMENT. The bit 4 and 5 of the ETC_EQUIPMENT are - - * zeros for EGA and VGA. However, the EGA/VGA BIOS will set - - * these bits in BIOSDATA_EQUIPMENT according to the monitor - - * type detected. - - */ - - switch ((rtcin(RTC_EQUIPMENT) >> 4) & 3) { /* bit 4 and 5 */ - - case 0: /* EGA/VGA, or nothing */ - - crtc_type = KD_EGA; - - /* the color adapter may be in the 40x25 mode... XXX */ - - break; - - case 1: /* CGA 40x25 */ - - /* switch to the 80x25 mode? XXX */ - - /* FALL THROUGH */ - - case 2: /* CGA 80x25 */ - - /* `crtc_type' has already been set... */ - - /* crtc_type = KD_CGA; */ - - break; - - case 3: /* MDA */ - - /* `crtc_type' has already been set... */ - - /* crtc_type = KD_MONO; */ - - break; - - } + if (crtc_type != KD_PIXEL) { + /* + * Check rtc and BIOS date area. + * XXX: don't use BIOSDATA_EQUIPMENT, it is not a dead copy + * of RTC_EQUIPMENT. The bit 4 and 5 of the ETC_EQUIPMENT are + * zeros for EGA and VGA. However, the EGA/VGA BIOS will set + * these bits in BIOSDATA_EQUIPMENT according to the monitor + * type detected. + */ + switch ((rtcin(RTC_EQUIPMENT) >> 4) & 3) { /* bit 4 and 5 */ + case 0: /* EGA/VGA, or nothing */ + crtc_type = KD_EGA; + /* the color adapter may be in the 40x25 mode... XXX */ + break; + case 1: /* CGA 40x25 */ + /* switch to the 80x25 mode? XXX */ + /* FALL THROUGH */ + case 2: /* CGA 80x25 */ + /* `crtc_type' has already been set... */ + /* crtc_type = KD_CGA; */ + break; + case 3: /* MDA */ + /* `crtc_type' has already been set... */ + /* crtc_type = KD_MONO; */ + break; + } - - /* is this a VGA or higher ? */ - - outb(crtc_addr, 7); - - if (inb(crtc_addr) == 7) { - - - - crtc_type = KD_VGA; - - crtc_vga = TRUE; - - read_vgaregs(vgaregs); - - - - /* Get the BIOS video mode pointer */ - - segoff = *(u_long *)pa_to_va(0x4a8); - - pa = (((segoff & 0xffff0000) >> 12) + (segoff & 0xffff)); - - if (ISMAPPED(pa, sizeof(u_long))) { - - segoff = *(u_long *)pa_to_va(pa); + /* is this a VGA or higher ? */ + outb(crtc_addr, 7); + if (inb(crtc_addr) == 7) { + + crtc_type = KD_VGA; + crtc_vga = TRUE; + read_vgaregs(vgaregs); + + /* Get the BIOS video mode pointer */ + segoff = *(u_long *)pa_to_va(0x4a8); pa = (((segoff & 0xffff0000) >> 12) + (segoff & 0xffff)); if (ISMAPPED(pa, MODE_PARAM_SIZE)) video_mode_ptr = (char *)pa_to_va(pa); @@ -728,6 +743,9 @@ case KD_CGA: printf("CGA"); break; + case KD_PIXEL: + printf("Graphics display (VESA mode = 0x%x)", vesa_mode); + break; case KD_MONO: case KD_HERCULES: default: @@ -1915,11 +1933,11 @@ return ENXIO; case PIO_FONT8x16: /* set 8x16 dot font */ - - if (!crtc_vga) + if (!crtc_vga && crtc_type != KD_PIXEL) return ENXIO; bcopy(data, font_16, 16*256); fonts_loaded |= FONT_16; - - if (!(cur_console->status & UNKNOWN_MODE)) { + if (crtc_vga && !(cur_console->status & UNKNOWN_MODE)) { copy_font(LOAD, FONT_16, font_16); if (flags & CHAR_CURSOR) set_destructive_cursor(cur_console); @@ -1927,7 +1945,7 @@ return 0; case GIO_FONT8x16: /* get 8x16 dot font */ - - if (!crtc_vga) + if (!crtc_vga && crtc_type != KD_PIXEL) return ENXIO; if (fonts_loaded & FONT_16) { bcopy(font_16, data, 16*256); @@ -2046,8 +2064,7 @@ s = splclock(); if (scp == cur_console && !(scp->status & UNKNOWN_MODE)) { if (/* timer not running && */ (scp->start <= scp->end)) { - - sc_bcopy(scp->scr_buf + scp->start, Crtat + scp->start, - - (1 + scp->end - scp->start) * sizeof(u_short)); + sc_bcopy(scp->scr_buf, scp->start, scp->end, 0); scp->start = scp->xsize * scp->ysize; scp->end = 0; } @@ -2159,8 +2176,7 @@ if (scrn_blanked <= 0) { /* update screen image */ if (scp->start <= scp->end) { - - sc_bcopy(scp->scr_buf + scp->start, Crtat + scp->start, - - (1 + scp->end - scp->start) * sizeof(u_short)); + sc_bcopy(scp->scr_buf, scp->start, scp->end, 0); } /* update "pseudo" mouse pointer image */ @@ -2354,6 +2370,9 @@ update_leds(new_scp->status); delayed_next_scr = FALSE; mark_all(new_scp); + if (vesa_mode == 0x102) { + bzero(Crtat, 800*600/8); + } } static void @@ -3104,8 +3123,9 @@ } /* copy screen to temporary buffer */ - - sc_bcopy(Crtat, sc_buffer, - - console[0]->xsize * console[0]->ysize * sizeof(u_short)); + if (crtc_type != KD_PIXEL) + generic_bcopy(Crtat, sc_buffer, + console[0]->xsize * console[0]->ysize * sizeof(u_short)); console[0]->scr_buf = console[0]->mouse_pos = sc_buffer; console[0]->cursor_pos = console[0]->cursor_oldpos = sc_buffer + hw_cursor; @@ -4322,7 +4342,7 @@ while (!(inb(crtc_addr+6) & 0x08)) /* wait for vertical retrace */ ; #endif set_font_mode(buf); - - sc_bcopy(cursor, (char *)pa_to_va(address) + DEAD_CHAR * 32, 32); + generic_bcopy(cursor, (char *)pa_to_va(address) + DEAD_CHAR * 32, 32); set_normal_mode(buf); } @@ -4623,7 +4643,7 @@ while (!(inb(crtc_addr+6) & 0x08)) /* idle */ ; #endif set_font_mode(buf); - - sc_bcopy(scp->mouse_cursor, (char *)pa_to_va(address) + 0xd0 * 32, 128); + generic_bcopy(scp->mouse_cursor, (char *)pa_to_va(address) + 0xd0 * 32, 128); set_normal_mode(buf); *(crt_pos) = (*(scp->mouse_pos)&0xff00)|0xd0; *(crt_pos+scp->xsize) = (*(scp->mouse_pos+scp->xsize)&0xff00)|0xd2; @@ -4750,6 +4770,33 @@ Crtat, scp->xsize * scp->ysize); blink_in_progress--; timeout(blink_screen, scp, hz / 10); + } +} + +void +sc_bcopy(u_short *p, int from, int to, int mark) +{ + if (!vesa_mode) { + generic_bcopy(p+from, Crtat+from, (to-from+1)*sizeof (u_short)); + } else if (vesa_mode == 0x102) { + u_char *d, *e; + int i,j; + + d = (u_char *)Crtat; + d += 10 + 6*16*100 + (from%80) + 16*100*(from/80); + for (i = from ; i <= to ; i++) { + e = d; + for (j = 0 ; j < 16; j++) { + if (mark) + *e = 255^font_16[(p[i]&0xff)*16+j]; + else + *e = font_16[(p[i]&0xff)*16+j]; + e+=100; + } + d++; + if ((i % 80) == 79) + d += 20 + 15*100; + } } } Index: i386/isa/syscons.h =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/syscons.h,v retrieving revision 1.36 diff -u -r1.36 syscons.h - --- syscons.h 1997/11/21 11:37:07 1.36 +++ syscons.h 1997/11/22 15:11:23 @@ -48,7 +48,7 @@ } #define mark_all(scp) {\ scp->start = 0;\ - - scp->end = scp->xsize * scp->ysize;\ + scp->end = scp->xsize * scp->ysize - 1;\ } /* status flags */ ------- Forwarded Message Return-Path: MAILER-DAEMON Received: from sz.cei.gov.cn ([203.207.179.2]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id LAA12195 for ; Sun, 14 Dec 1997 11:35:38 +0100 (CET) (envelope-from ) Received: from localhost (localhost) by sz.cei.gov.cn (8.7.5+2.6Wbeta6/3.4W CEI-LN 96090315) with internal id SAA08604; Sun, 14 Dec 1997 18:43:07 +0800 (CST) Date: Sun, 14 Dec 1997 18:43:07 +0800 (CST) From: Mail Delivery Subsystem Subject: Returned mail: Local configuration error Message-Id: <199712141043.SAA08604@sz.cei.gov.cn> To: postmaster@sz.cei.gov.cn To: Auto-Submitted: auto-generated (failure) The original message was received at Sun, 14 Dec 1997 18:42:52 +0800 (CST) from critter.freebsd.dk [195.8.129.26] ----- The following addresses have delivery notifications ----- (unrecoverable error) ----- Transcript of session follows ----- 553 szup2.sz.cei.go.cn. config error: mail loops back to me (MX problem?) 554 ... Local configuration error ----- Original message follows ----- Return-Path: phk@critter.freebsd.dk Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by sz.cei.gov.cn (8.7.5+2.6Wbeta6/3.4W CEI-LN 96090315) with ESMTP id SAA08602 for ; Sun, 14 Dec 1997 18:42:52 +0800 (CST) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id LAA12175 for ; Sun, 14 Dec 1997 11:33:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Deng Hongwei Subject: Re: Help the patch for 800x600x16 boot -current In-reply-to: Your message of "Sun, 14 Dec 1997 06:14:36 +0800." <349308CC.FD11DC6D@sz.cei.go.cn> Date: Sun, 14 Dec 1997 11:33:39 +0100 Message-ID: <12173.882095619@critter.freebsd.dk> From: Poul-Henning Kamp -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-mobile Sun Dec 14 17:14:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA00986 for mobile-outgoing; Sun, 14 Dec 1997 17:14:27 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA00981 for ; Sun, 14 Dec 1997 17:14:22 -0800 (PST) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id KAA01846; Mon, 15 Dec 1997 10:14:18 +0900 (JST) Date: Mon, 15 Dec 1997 10:14:18 +0900 (JST) Message-Id: <199712150114.KAA01846@afs.ntc.mita.keio.ac.jp> To: mobile@freebsd.org Cc: hosokawa@ntc.keio.ac.jp Subject: Multifunction PC-card support From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I started the implementation of multifunction PC-card support on FreeBSD based on extended PC-card specification. I have only Motorola's Mariner PC-card Ethernet/28.8K modem card (I also have Megahertz's multifunction card, but it's very old card, so I think it isn't compatible the extended PC-card specification). If you have any information about this card, please answer the following questions. 1. Is Motorola Mariner extended PC-card spec compatible? 2. Is Ethernet function of Motorola Mariner is compatible with NE2000? -- HOSOKAWA, Tatsumi Network Technology Center Keio University hosokawa@ntc.keio.ac.jp From owner-freebsd-mobile Sun Dec 14 17:32:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02422 for mobile-outgoing; Sun, 14 Dec 1997 17:32:46 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA02415 for ; Sun, 14 Dec 1997 17:32:43 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xhPOf-0007B3-00; Sun, 14 Dec 1997 18:32:37 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id SAA26451 for ; Sun, 14 Dec 1997 18:32:27 -0700 (MST) Message-Id: <199712150132.SAA26451@harmony.village.org> To: mobile@freebsd.org Subject: Silly question Date: Sun, 14 Dec 1997 18:32:27 -0700 From: Warner Losh Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK. Let's say I wanted to be silly and run my Libretto off of 10 D batteries rather than the nice LiIon battery that it came with. does anybody see a problem doing this? Basically, I'd plug them into the 15V power jack on the libretto. Comments? Warner P.S. I'm doing this to have the option of getting lots of batteries at the airport when the normal and extended life batteries are drained and I don't have time to recharge them. From owner-freebsd-mobile Sun Dec 14 18:04:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA05806 for mobile-outgoing; Sun, 14 Dec 1997 18:04:51 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA05789 for ; Sun, 14 Dec 1997 18:04:45 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id MAA00460; Mon, 15 Dec 1997 12:29:26 +1030 (CST) Message-Id: <199712150159.MAA00460@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Warner Losh cc: mobile@FreeBSD.ORG Subject: Re: Silly question In-reply-to: Your message of "Sun, 14 Dec 1997 18:32:27 PDT." <199712150132.SAA26451@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Dec 1997 12:29:25 +1030 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > OK. Let's say I wanted to be silly and run my Libretto off of 10 D > batteries rather than the nice LiIon battery that it came with. does > anybody see a problem doing this? Basically, I'd plug them into the > 15V power jack on the libretto. The current draw is likely to kill them dead pretty quickly. D batteries aren't what you'd describe as "wonderful". Still, it should work, yes. > P.S. I'm doing this to have the option of getting lots of batteries > at the airport when the normal and extended life batteries are drained > and I don't have time to recharge them. Go sit in the toilet for an hour & use the power point there. 8) mike From owner-freebsd-mobile Sun Dec 14 18:09:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06295 for mobile-outgoing; Sun, 14 Dec 1997 18:09:53 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from u1.farm.idt.net (root@u1.farm.idt.net [169.132.8.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06288 for ; Sun, 14 Dec 1997 18:09:49 -0800 (PST) (envelope-from garycorc@idt.net) Received: from idt.net (ppp-23.ts-1.mlb.idt.net [169.132.71.23]) by u1.farm.idt.net (8.8.8/8.8.5) with ESMTP id VAA06540; Sun, 14 Dec 1997 21:09:36 -0500 (EST) Message-ID: <34949112.BB3779D5@idt.net> Date: Sun, 14 Dec 1997 21:08:18 -0500 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.03 [en] (Win95; U) MIME-Version: 1.0 To: Warner Losh CC: mobile@freebsd.org Subject: Re: Silly question References: <199712150132.SAA26451@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Warner Losh wrote: > > OK. Let's say I wanted to be silly and run my Libretto off of 10 D > batteries rather than the nice LiIon battery that it came with. does > anybody see a problem doing this? Basically, I'd plug them into the > 15V power jack on the libretto. > > Comments? > > Warner > > P.S. I'm doing this to have the option of getting lots of batteries > at the airport when the normal and extended life batteries are drained > and I don't have time to recharge them. Electrically, that should be fine. Economically is another matter... ;-) You might want to check what voltage you Li-Ion battery is. Since there's usually margin on the 15V DC input so that you can run it off a simple car converter circuit that may be putting out 15V when the car is running but only 12V when the engine is off, you may be able to get by with, say, only 8 D cells. I'd try (at home) running off fewer D cells and see if that works for you... Gary From owner-freebsd-mobile Sun Dec 14 18:48:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA10120 for mobile-outgoing; Sun, 14 Dec 1997 18:48:03 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA10097 for ; Sun, 14 Dec 1997 18:47:55 -0800 (PST) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id NAA07465; Mon, 15 Dec 1997 13:17:39 +1030 (CST) (envelope-from grog) Message-ID: <19971215131739.34935@lemis.com> Date: Mon, 15 Dec 1997 13:17:39 +1030 From: Greg Lehey To: Mike Smith Cc: Warner Losh , mobile@FreeBSD.ORG Subject: Re: Silly question References: <199712150132.SAA26451@harmony.village.org> <199712150159.MAA00460@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199712150159.MAA00460@word.smith.net.au>; from Mike Smith on Mon, Dec 15, 1997 at 12:29:25PM +1030 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Dec 15, 1997 at 12:29:25PM +1030, Mike Smith wrote: >> >> P.S. I'm doing this to have the option of getting lots of batteries >> at the airport when the normal and extended life batteries are drained >> and I don't have time to recharge them. > > Go sit in the toilet for an hour & use the power point there. 8) I've never had problems finding a power point in a departure lounge. My problem is to have the correct kind of plug :-) Which airports are you concerned about? Greg From owner-freebsd-mobile Sun Dec 14 20:18:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA16799 for mobile-outgoing; Sun, 14 Dec 1997 20:18:04 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA16794 for ; Sun, 14 Dec 1997 20:18:01 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA17386; Sun, 14 Dec 1997 21:17:59 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA03645; Sun, 14 Dec 1997 21:17:57 -0700 Date: Sun, 14 Dec 1997 21:17:57 -0700 Message-Id: <199712150417.VAA03645@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) Cc: mobile@freebsd.org Subject: Re: Multifunction PC-card support In-Reply-To: <199712150114.KAA01846@afs.ntc.mita.keio.ac.jp> References: <199712150114.KAA01846@afs.ntc.mita.keio.ac.jp> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I started the implementation of multifunction PC-card support on > FreeBSD based on extended PC-card specification. I'd be very intersted in knowing how you are doing that, and how you plan on changing things in /sys/pccard. I'm sure Mike is as well, since this is functionality FreeBSD sorely needs. Nate From owner-freebsd-mobile Sun Dec 14 20:20:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA16995 for mobile-outgoing; Sun, 14 Dec 1997 20:20:14 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA16985 for ; Sun, 14 Dec 1997 20:20:09 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA17404; Sun, 14 Dec 1997 21:20:08 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA03653; Sun, 14 Dec 1997 21:20:07 -0700 Date: Sun, 14 Dec 1997 21:20:07 -0700 Message-Id: <199712150420.VAA03653@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: mobile@freebsd.org Subject: Re: Silly question In-Reply-To: <199712150132.SAA26451@harmony.village.org> References: <199712150132.SAA26451@harmony.village.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > OK. Let's say I wanted to be silly and run my Libretto off of 10 D > batteries rather than the nice LiIon battery that it came with. does > anybody see a problem doing this? Basically, I'd plug them into the > 15V power jack on the libretto. > > Comments? Make sure you got a good voltage regulator on it and it should work fine. Batteries tend to get a bit weird towards the end, so a voltage regulator is necessary to keep things nice and stable so you don't get any weird power problems. Personally, I'd spend the $$ and get a couple extra batteries for the thing. They're *ALOT* lighter than 10-D batteries, have a longer life, and don't defeat the purpose of having a really light laptop and a really heavy battery pack. :) :) Nate From owner-freebsd-mobile Sun Dec 14 20:53:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA18846 for mobile-outgoing; Sun, 14 Dec 1997 20:53:43 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA18782 for ; Sun, 14 Dec 1997 20:52:02 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xhSVb-0007Fn-00; Sun, 14 Dec 1997 21:51:59 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id VAA05804; Sun, 14 Dec 1997 21:51:51 -0700 (MST) Message-Id: <199712150451.VAA05804@harmony.village.org> To: Greg Lehey Subject: Re: Silly question Cc: Mike Smith , mobile@freebsd.org In-reply-to: Your message of "Mon, 15 Dec 1997 13:17:39 +1030." <19971215131739.34935@lemis.com> References: <19971215131739.34935@lemis.com> <199712150132.SAA26451@harmony.village.org> <199712150159.MAA00460@word.smith.net.au> Date: Sun, 14 Dec 1997 21:51:50 -0700 From: Warner Losh Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <19971215131739.34935@lemis.com> Greg Lehey writes: : I've never had problems finding a power point in a departure lounge. : My problem is to have the correct kind of plug :-) Which airports are : you concerned about? Well, I don't worry about the plugs in the US. However, I searched for 20 minutes looking for a working power plug at Heathrow a little while ago... Found several, even had the right adapter (at least I think so, it worked at the hotel and a friend's house), but it appears that none of the outlets at the airport had actual power to them... Warner From owner-freebsd-mobile Sun Dec 14 22:03:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA23665 for mobile-outgoing; Sun, 14 Dec 1997 22:03:15 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA23468 for ; Sun, 14 Dec 1997 22:00:53 -0800 (PST) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id OAA02926; Mon, 15 Dec 1997 14:57:34 +0900 (JST) Date: Mon, 15 Dec 1997 14:57:34 +0900 (JST) Message-Id: <199712150557.OAA02926@afs.ntc.mita.keio.ac.jp> To: nate@mt.sri.com Cc: mobile@freebsd.org, hosokawa@ntc.keio.ac.jp Subject: Re: Multifunction PC-card support In-Reply-To: Your message of "Sun, 14 Dec 1997 21:17:57 -0700". <199712150417.VAA03645@mt.sri.com> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199712150417.VAA03645@mt.sri.com> nate@mt.sri.com writes: >> > I started the implementation of multifunction PC-card support on >> > FreeBSD based on extended PC-card specification. >> >> I'd be very intersted in knowing how you are doing that, and how you >> plan on changing things in /sys/pccard. I'm sure Mike is as well, since >> this is functionality FreeBSD sorely needs. I only started reading CIS tupples of Mariner card. But unfortunately pccardc dumpcis says that this card has following CIS tupples. -------------------------------------------------------------------------- Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x15 (Version 1 info), length = 56 000: 04 01 4d 6f 74 6f 72 6f 6c 61 2c 20 49 6e 63 2e 010: 00 4d 41 52 49 4e 45 52 20 4d 4f 44 45 4d 2f 46 020: 41 58 2f 4c 41 4e 00 56 65 72 2e 20 31 2e 32 2e 030: 30 34 30 38 39 36 00 ff Version = 4.1, Manuf = [Motorola, Inc.],card vers = [MARINER MODEM/FAX/LAN] Addit. info = [Ver. 1.2.040896],[] Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 09 01 01 05 PCMCIA ID = 0x109, OEM ID = 0x501 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 02 00 Serial port/modem Tuple #5, code = 0x22 (Functional EXT), length = 4 000: 00 02 0f 1c Serial interface extension: 16550 UART, Parity - Space,Mark,Odd,Even, Tuple #6, code = 0x22 (Functional EXT), length = 11 000: 01 1f 1e 00 04 00 00 00 04 00 00 Modem interface capabilities: Tuple #7, code = 0x22 (Functional EXT), length = 14 000: 02 06 00 3f 1c 02 03 1f 06 00 00 b5 20 00 Data modem services available: Tuple #8, code = 0x22 (Functional EXT), length = 9 000: 06 1f 1e 00 04 00 00 04 00 Modem interface capabilities: Tuple #9, code = 0x22 (Functional EXT), length = 10 000: 13 06 00 0f 00 00 00 b5 20 00 Tuple #10, code = 0x22 (Functional EXT), length = 10 000: 23 06 00 0f 00 00 00 b5 20 00 Tuple #11, code = 0x1a (Configuration map), length = 5 000: 01 45 20 80 77 Reg len = 2, config register addr = 0x8020, last config = 0x45 Registers: XXX-XXX- Tuple #12, code = 0x1b (Configuration entry), length = 18 000: c5 01 99 71 55 1e 4e 23 aa 60 f8 03 07 30 bc 9e 010: 28 00 Config index = 0x5(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 1.5 x 100mA Max current average over 10 ms: 4.5 x 100mA Power down supply current: 2 x 100uA Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level IRQs: 2 3 4 5 7 9 10 11 12 15 Max twin cards = 0 Misc attr: (Audio-BVD2) (Power down supported) Tuple #13, code = 0x1b (Configuration entry), length = 7 000: 25 08 aa 60 f8 02 07 Config index = 0x25 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 Tuple #14, code = 0x1b (Configuration entry), length = 7 000: 35 08 aa 60 e8 03 07 Config index = 0x35 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 Tuple #15, code = 0x1b (Configuration entry), length = 7 000: 45 08 aa 60 e8 02 07 Config index = 0x5(default) Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 Tuple #16, code = 0xff (Terminator), length = 0 2 slots found -------------------------------------------------------------------------- PC-card standard says that Multifunction CIS has CISTPL_LONGLINK_MFC (0x06) tupple. According to this output, this card has no 0x06 longlink tupples in it. Morever, it says that this card is "Serial port/modem" only (ID of multifunction card is 0). I think that this card is NOT compatible with PC-card standard multifunction support. Therefore, some sort of dirty hack is needed. According to tupple #11, configuration register of a function (maybe it's serial function, because this card is can be used as serial card without modification of FreeBSD PC-card support) is placed at 0x8020. Looked round attribute memory 0x8020 by pccardc rdattr, I found: -------------------------------------------------------------------------- 7fc0: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 7fd0: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 7fe0: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 7ff0: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 8000: 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8020: 45 00 80 00 22 00 00 00 00 00 00 00 00 00 00 00 8030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -------------------------------------------------------------------------- 0x8020 seems to be configuration registers of PC-card, but 0x8000 also seems to be configuration registers. So, I think that 0x8000 is configuration registers of another function (maybe Ethernet). Also looking round attribute memory of this CIS, I found another garbage bytes follows normal CIS tupples. -------------------------------------------------------------------------- 0160: 02 00 07 00 1b 00 07 00 35 00 08 00 aa 00 60 00 0170: e8 00 03 00 07 00 1b 00 07 00 45 00 08 00 aa 00 0180: 60 00 e8 00 02 00 07 00 ff 00 ff 00 00 00 00 00 ~~ end of CIS (0xff) 0190: 06 00 af 00 ba 00 47 00 0c 00 57 00 a4 00 58 00 01a0: 00 00 01 00 07 00 57 00 04 00 07 00 90 00 b3 00 01b0: 1f 00 7a 00 af 00 30 00 af 00 00 00 4b 00 8f 00 01c0: ef 00 11 00 c9 00 34 00 00 00 04 00 00 00 30 00 01d0: af 00 57 00 a5 00 ab 00 77 00 f6 00 2f 00 07 00 01e0: 04 00 00 00 00 00 af 00 b5 00 91 00 27 00 f6 00 01f0: 2f 00 04 00 04 00 af 00 c7 00 d6 00 27 00 b6 00 0200: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 0210: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 0220: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 0230: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 0240: ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 -------------------------------------------------------------------------- I don't know how to decode this enigma, and perhaps it's really a garbage :-<. If you can decode this, please tell me the truth :-). Anyway, according to PC-card standard, multifunction IRQ shareing can be identified by searching all function's Intr bit of configuration option register. PC-card support of FreeBSD already has pcicintr() first level interrupt handler. So I think it's not difficult to add the code that identify which function's Intr bit, dispatch the interrupt request to the appropriate second-level interrupt handler. Moreover, according to PC-card standard bit 2-0 of config index of multifunction card means, bit 0: enable/disable this function bit 1: number of I/O addresss used bit 2: enables IREQ# routing So, default config index 0x05 means that it enable this function and enable IREQ# routing. All config index has 0x05 bits, so I 'feel' this card partly compatible with PC-card standard. I'll hack this card and try to write first level interrupt handler this month. -- HOSOKAWA, Tatsumi Network Technology Center Keio University hosokawa@ntc.keio.ac.jp From owner-freebsd-mobile Mon Dec 15 00:43:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA06479 for mobile-outgoing; Mon, 15 Dec 1997 00:43:01 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA06474 for ; Mon, 15 Dec 1997 00:42:53 -0800 (PST) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id TAA01383; Mon, 15 Dec 1997 19:12:31 +1030 (CST) (envelope-from grog) Message-ID: <19971215191231.48430@lemis.com> Date: Mon, 15 Dec 1997 19:12:31 +1030 From: Greg Lehey To: Warner Losh Cc: Mike Smith , mobile@FreeBSD.ORG Subject: Re: Silly question References: <19971215131739.34935@lemis.com> <199712150132.SAA26451@harmony.village.org> <199712150159.MAA00460@word.smith.net.au> <19971215131739.34935@lemis.com> <199712150451.VAA05804@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199712150451.VAA05804@harmony.village.org>; from Warner Losh on Sun, Dec 14, 1997 at 09:51:50PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Dec 14, 1997 at 09:51:50PM -0700, Warner Losh wrote: > In message <19971215131739.34935@lemis.com> Greg Lehey writes: >> I've never had problems finding a power point in a departure lounge. >> My problem is to have the correct kind of plug :-) Which airports are >> you concerned about? > > Well, I don't worry about the plugs in the US. Yes, I understand. > However, I searched for 20 minutes looking for a working power plug > at Heathrow a little while ago... Found several, even had the right > adapter (at least I think so, it worked at the hotel and a friend's > house), but it appears that none of the outlets at the airport had > actual power to them... Well, I think Heathrow is bottom on my list anyway. I was at Gatwick a few months back, and had no trouble there. I even had an adaptor. Greg From owner-freebsd-mobile Mon Dec 15 05:08:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA25586 for mobile-outgoing; Mon, 15 Dec 1997 05:08:31 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from didda.est.is (ppp-22.est.is [194.144.208.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA25571 for ; Mon, 15 Dec 1997 05:08:15 -0800 (PST) (envelope-from totii@est.is) Received: from est.is (didda.est.is [192.168.255.1]) by didda.est.is (8.8.7/8.8.7) with ESMTP id NAA01130; Mon, 15 Dec 1997 13:06:11 GMT (envelope-from totii@est.is) Message-ID: <34952B43.238DA455@est.is> Date: Mon, 15 Dec 1997 13:06:11 +0000 From: "Þorður Ivarsson" X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Warner Losh CC: Greg Lehey , Mike Smith , mobile@FreeBSD.ORG Subject: Re: Silly question References: <19971215131739.34935@lemis.com> <199712150132.SAA26451@harmony.village.org> <199712150159.MAA00460@word.smith.net.au> <199712150451.VAA05804@harmony.village.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Warner Losh wrote: > > In message <19971215131739.34935@lemis.com> Greg Lehey writes: > : I've never had problems finding a power point in a departure lounge. > : My problem is to have the correct kind of plug :-) Which airports are > : you concerned about? > > Well, I don't worry about the plugs in the US. However, I searched > for 20 minutes looking for a working power plug at Heathrow a little > while ago... Found several, even had the right adapter (at least I > think so, it worked at the hotel and a friend's house), but it appears > that none of the outlets at the airport had actual power to them... I must have been hydro power in the outlets :) If you connect the batteries to the battery connectors of the laptop you will get longet lifetime of the D-cells because of the psu/charger in the laptop. Measure the laptop battery and use similar voltage from the D-cells (disels :) ) -- Þórður Ívarsson Thordur Ivarsson Rafeindavirki Electronic technician Norðurgötu 30 Nordurgotu 30 Box 309 Box 309 602 Akureyri 602 Akureyri Ísland Iceland --------------------------------------------- FreeBSD has good features, Some others are full of unwanted features! --------------------------------------------- From owner-freebsd-mobile Mon Dec 15 09:03:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA13515 for mobile-outgoing; Mon, 15 Dec 1997 09:03:11 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA13498 for ; Mon, 15 Dec 1997 09:03:03 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA10657; Mon, 15 Dec 1997 09:01:41 -0800 (PST) Received: from UNKNOWN(), claiming to be "crab.whistle.com" via SMTP by alpo.whistle.com, id smtpd010655; Mon Dec 15 09:01:39 1997 Received: (from ambrisko@localhost) by crab.whistle.com (8.8.8/8.6.12) id IAA05661; Mon, 15 Dec 1997 08:58:12 -0800 (PST) From: Doug Ambrisko Message-Id: <199712151658.IAA05661@crab.whistle.com> Subject: Re: Cardbus controller status request / notebook update In-Reply-To: <199712130232.SAA11402@tnt.isi.edu> from Ted Faber at "Dec 12, 97 06:32:22 pm" To: faber@ISI.EDU (Ted Faber) Date: Mon, 15 Dec 1997 08:58:12 -0800 (PST) Cc: ambrisko@whistle.com, nate@mt.sri.com, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ted Faber writes: | Doug Ambrisko wrote: | >I guess my question is, that when booting -v with a 6832 what does the | >probe return for the port of the 6832? On my card it returned 0. Then | >when it set the emulation to work at port 0, it didn't work. | | Hurm. Now *thatt's weird. I'll take a look tomorrow, but I think | your card has some funny defaults set. Your override looked OK, but I Yep. I wouldn't rush in my patches yet, since this week I expect to get the programing doc. I sent my patch incase other people might be having trouble since the latest PAO stuff also set this register. | >a bit odd. I have a 6832 eval card that goes into a PCI slot. A cable | >goes from this card to an ISA card to trigger ISA interrupts. Kind-of neat. | >Unfortunately I didn't get any programming doc's with this card so I need | >to ask for them. I have a belief that some laptop BIOS's have the code | >to set this stuff up so old drivers work with the new chip. Since, I'm | >just using a standard old PC my BIOS doesn't touch it. | | Ye Gods, man, where'd you get *that* thing. :-) :-) >From Cirrus Logic. | Seriously, any sign of documentation for it? Can you tell me what | board it is? I expect to get doc this week or next. I've requested it via our contact. Then hopefully I'll have a definition of all the registers on the chip! | Your guess about BIOS setup being fritzed may be true. Is the thing | PnP? Maybe we can init it through Luigi's PnP stuff. Maybe I haven't checked that. I could see what it shows up. On one of the floppies they have a com file to setup the card. I may try to disassemble it and figure out what it does (it's only 977 bytes). I tried running it under DOS and then rebooting with FreeBSD and that didn't help. | Take all of that with a grain of salt, I'll know the right questions | to ask once I look over the code tomorrow. Any ideas are helpful. Doug A. From owner-freebsd-mobile Mon Dec 15 12:22:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09215 for mobile-outgoing; Mon, 15 Dec 1997 12:22:33 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from cs.uoregon.edu (vitalstatistix.cs.uoregon.edu [128.223.200.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09194 for ; Mon, 15 Dec 1997 12:22:20 -0800 (PST) (envelope-from zappala@cs.uoregon.edu) Received: from cs.uoregon.edu (suffix.cs.uoregon.edu [128.223.200.37]) by cs.uoregon.edu (8.8.7/8.8.5) with ESMTP id MAA09528; Mon, 15 Dec 1997 12:22:13 -0800 (PST) Message-Id: <199712152022.MAA09528@cs.uoregon.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: freebsd-mobile@freebsd.org, Nate Williams cc: zappala@cs.uoregon.edu Subject: Re: Cardbus controller status request / notebook update In-reply-to: Your message of "Thu, 11 Dec 1997 17:11:14 PST." <199712120011.RAA24355@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Dec 1997 12:22:13 -0800 From: Daniel Zappala Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > Also, if you can get docs on the newer chipsets and post pointers to > > > them here or somehow make them available if/when I get someone willing > > > to work with me who has the hardware or who is willing to do the work by > > > themselves we can support newer PCI chipsets in PCMCIA emulation mode. > > > > All I got was the data sheet from TI's web site. I don't know if that > > is sufficient to do the programming or if there is some other resource > > for working with the chip's registers. > > Can you give me a pointer to it. The TP560X uses the TI 1250A as its PC Card controller. I have the data sheet for this chip, which i grabbed from http://www-s.ti.com/sc/psheets/xcps014/xcps014.pdf There is an article on it at: http://www.ti.com/sc/docs/msp/showcase/vol24/page14.htm Daniel From owner-freebsd-mobile Mon Dec 15 14:16:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20752 for mobile-outgoing; Mon, 15 Dec 1997 14:16:53 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from cs.uoregon.edu (vitalstatistix.cs.uoregon.edu [128.223.8.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20743 for ; Mon, 15 Dec 1997 14:16:50 -0800 (PST) (envelope-from zappala@cs.uoregon.edu) Received: from cs.uoregon.edu (suffix.cs.uoregon.edu [128.223.200.37]) by cs.uoregon.edu (8.8.7/8.8.5) with ESMTP id OAA11901; Mon, 15 Dec 1997 14:16:45 -0800 (PST) Message-Id: <199712152216.OAA11901@cs.uoregon.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: Daniel Zappala cc: freebsd-mobile@freebsd.org Subject: Re: Cardbus controller status request / notebook update In-reply-to: Your message of "Mon, 15 Dec 1997 12:22:13 PST." <199712152022.MAA09528@cs.uoregon.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Dec 1997 14:16:44 -0800 From: Daniel Zappala Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The TP560X uses the TI 1250A as its PC Card controller. I have the data > sheet for this chip, which i grabbed from > > http://www-s.ti.com/sc/psheets/xcps014/xcps014.pdf > > There is an article on it at: > > http://www.ti.com/sc/docs/msp/showcase/vol24/page14.htm I just called TI and had them send me the complete manual for the chip. They mailed me a pdf file and I can forward it to you if you are interested. It's 114 pages and lists all the registers and their functions, so I think this is what I would need to write a driver for this chip. Am very close to deciding to do just that. Daniel Zappala zappala@cs.uoregon.edu From owner-freebsd-mobile Mon Dec 15 15:02:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA24649 for mobile-outgoing; Mon, 15 Dec 1997 15:02:47 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA24627 for ; Mon, 15 Dec 1997 15:02:37 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-s.isi.edu [128.9.192.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id PAA06062; Mon, 15 Dec 1997 15:02:31 -0800 (PST) Message-Id: <199712152302.PAA06062@tnt.isi.edu> To: Doug Ambrisko Cc: nate@mt.sri.com, freebsd-mobile@FreeBSD.ORG Subject: Re: Cardbus controller status request / notebook update In-Reply-To: Your message of "Mon, 15 Dec 1997 08:58:12 PST." <199712151658.IAA05661@crab.whistle.com> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Dec 1997 15:02:31 -0800 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Doug Ambrisko wrote: >Ted Faber writes: >| Doug Ambrisko wrote: >| >I guess my question is, that when booting -v with a 6832 what does the >| >probe return for the port of the 6832? On my card it returned 0. Then >| >when it set the emulation to work at port 0, it didn't work. >| >| Hurm. Now *thatt's weird. I'll take a look tomorrow, but I think >| your card has some funny defaults set. Your override looked OK, but I > >Yep. I wouldn't rush in my patches yet, since this week I expect to >get the programing doc. I sent my patch incase other people might be >having trouble since the latest PAO stuff also set this register. Doug, can I get a dump from a bootverbose boot of the unmodified kernel? I'd like to see all the Cardbus registers. Thanks! - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNJW3BYb4eisfQ5rpAQHu6gP9HgjdpBsYolxXoulnD2j9GlEWkKLbz2WL JTagbLJvO/P+QIhx3lZfL5Efe4g2zLhHynB+Fp9+bqkz7umsdlkki3NUcNUxS4o1 bedxSE3V10dXeCNLgKR04WTQ5XSMCy9Mrbbxt7cngDg08JloWz1Vty4/hOzSE8hA hoJ1sB98BGI= =kAyu -----END PGP SIGNATURE----- From owner-freebsd-mobile Mon Dec 15 16:43:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA03533 for mobile-outgoing; Mon, 15 Dec 1997 16:43:40 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA03512 for ; Mon, 15 Dec 1997 16:43:34 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA24797; Mon, 15 Dec 1997 17:43:32 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA06928; Mon, 15 Dec 1997 17:43:29 -0700 Date: Mon, 15 Dec 1997 17:43:29 -0700 Message-Id: <199712160043.RAA06928@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Daniel Zappala Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Cardbus controller status request / notebook update In-Reply-To: <199712152216.OAA11901@cs.uoregon.edu> References: <199712152022.MAA09528@cs.uoregon.edu> <199712152216.OAA11901@cs.uoregon.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The TP560X uses the TI 1250A as its PC Card controller. I have the data > > sheet for this chip, which i grabbed from > > > > http://www-s.ti.com/sc/psheets/xcps014/xcps014.pdf > > > > There is an article on it at: > > > > http://www.ti.com/sc/docs/msp/showcase/vol24/page14.htm > > I just called TI and had them send me the complete manual for the chip. > They mailed me a pdf file and I can forward it to you if you are interested. > It's 114 pages and lists all the registers and their functions, so I think > this is what I would need to write a driver for this chip. Am very close > to deciding to do just that. If you're going to do that, then there's no need for us to worry about it, right? *grin* Nate From owner-freebsd-mobile Mon Dec 15 18:43:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA13253 for mobile-outgoing; Mon, 15 Dec 1997 18:43:43 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA13244; Mon, 15 Dec 1997 18:43:38 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA25649; Mon, 15 Dec 1997 18:43:45 -0800 Date: Mon, 15 Dec 1997 18:43:45 -0800 (PST) From: Brian Handy To: Paul Traina Cc: mobile@freebsd.org Subject: Re: cvs commit: src/etc pccard_ether In-Reply-To: <199712160225.SAA24075@freefall.freebsd.org> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Dec 1997, Paul Traina wrote: >pst 1997/12/15 18:25:37 PST > > Modified files: > etc pccard_ether > Log: > Support ISC-DHCP if the package is available. Without having seen the patch (or paid attention to any discussion) this looks like it'll work with -stable as well...any reason for me not to believe that? Wondering, Brian From owner-freebsd-mobile Mon Dec 15 23:05:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA01468 for mobile-outgoing; Mon, 15 Dec 1997 23:05:06 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from noether.blah.org (slmel12p25.ozemail.com.au [203.108.200.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA01449 for ; Mon, 15 Dec 1997 23:04:58 -0800 (PST) (envelope-from ada@not-enough.bandwidth.org) Received: (from ada@localhost) by noether.blah.org (8.8.7/8.8.8) id SAA04231 for mobile@freebsd.org; Tue, 16 Dec 1997 18:04:05 +1100 (EST) From: Ada Message-Id: <199712160704.SAA04231@noether.blah.org> Subject: nokia cellular To: mobile@freebsd.org Date: Tue, 16 Dec 1997 18:04:05 +1100 (EST) Reply-To: ada@bsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anybody gotten the nokia cellular data stuff to work? (Any of it? I think one emulates a modem.) Ada. -- "No one can make you feel inferior without your consent." -- Eleanor Roosevelt From owner-freebsd-mobile Mon Dec 15 23:46:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA04167 for mobile-outgoing; Mon, 15 Dec 1997 23:46:24 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA04159 for ; Mon, 15 Dec 1997 23:46:18 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id SAA01377; Tue, 16 Dec 1997 18:10:41 +1030 (CST) Message-Id: <199712160740.SAA01377@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: ada@bsd.org cc: mobile@FreeBSD.ORG Subject: Re: nokia cellular In-reply-to: Your message of "Tue, 16 Dec 1997 18:04:05 +1100." <199712160704.SAA04231@noether.blah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Dec 1997 18:10:40 +1030 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Has anybody gotten the nokia cellular data stuff to work? > (Any of it? I think one emulates a modem.) >From the (poor) documentation I've seen so far, the Windows driver emulates a serial port, but the actual interface to the phone is different again. There appears to be a standard for the interface, but no sign of a document describing it, only a single vendor selling the driver software. Determining the protocol should be relatively straightforward given the right tools. From there, the rest is a SMOP. mike From owner-freebsd-mobile Tue Dec 16 00:07:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA05233 for mobile-outgoing; Tue, 16 Dec 1997 00:07:31 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from noether.blah.org (slmel12p25.ozemail.com.au [203.108.200.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA05218 for ; Tue, 16 Dec 1997 00:07:21 -0800 (PST) (envelope-from ada@not-enough.bandwidth.org) Received: (from ada@localhost) by noether.blah.org (8.8.7/8.8.8) id TAA05373; Tue, 16 Dec 1997 19:05:31 +1100 (EST) From: Ada Message-Id: <199712160805.TAA05373@noether.blah.org> Subject: Re: nokia cellular In-Reply-To: <199712160740.SAA01377@word.smith.net.au> from Mike Smith at "Dec 16, 97 06:10:40 pm" To: mike@smith.net.au (Mike Smith) Date: Tue, 16 Dec 1997 19:05:31 +1100 (EST) Cc: mobile@freebsd.org Reply-To: ada@bsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >From the (poor) documentation I've seen so far, the Windows driver > emulates a serial port, but the actual interface to the phone is > different again. There appears to be a standard for the interface, but > no sign of a document describing it, only a single vendor selling the > driver software. Are you talking about the pcmcia card? nokia also sell something called the 'cellular data suite' which utilises the serial port to talk. Ada. -- "'I wish life was not so short,' he thought. 'Languages take such a time, and so do all the things one wants to know about.'" -- J. R. R. Tolkien, _The Lost Road_ From owner-freebsd-mobile Tue Dec 16 00:12:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA05643 for mobile-outgoing; Tue, 16 Dec 1997 00:12:05 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA05598 for ; Tue, 16 Dec 1997 00:11:58 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id SAA01458; Tue, 16 Dec 1997 18:35:59 +1030 (CST) Message-Id: <199712160805.SAA01458@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: ada@bsd.org cc: mike@smith.net.au (Mike Smith), mobile@freebsd.org Subject: Re: nokia cellular In-reply-to: Your message of "Tue, 16 Dec 1997 19:05:31 +1100." <199712160805.TAA05373@noether.blah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Dec 1997 18:35:58 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >From the (poor) documentation I've seen so far, the Windows driver > > emulates a serial port, but the actual interface to the phone is > > different again. There appears to be a standard for the interface, but > > no sign of a document describing it, only a single vendor selling the > > driver software. > Are you talking about the pcmcia card? nokia also sell something called > the 'cellular data suite' which utilises the serial port to talk. Er, I haven't met the PCCARD adapter, I've only seen the serial port stuff. mike From owner-freebsd-mobile Tue Dec 16 03:54:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA19698 for mobile-outgoing; Tue, 16 Dec 1997 03:54:29 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA19693 for ; Tue, 16 Dec 1997 03:54:20 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id LAA12862; Tue, 16 Dec 1997 11:52:54 GMT Date: Tue, 16 Dec 1997 11:52:53 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: ada@bsd.org cc: mobile@freebsd.org Subject: Re: nokia cellular In-Reply-To: <199712160704.SAA04231@noether.blah.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 16 Dec 1997, Ada wrote: > Has anybody gotten the nokia cellular data stuff to work? > (Any of it? I think one emulates a modem.) The PCMCIA card certainly works - it does indeed look just like a modem (and if you prise open the lid on the card, you will find a real 16C550 inside!). From owner-freebsd-mobile Tue Dec 16 07:15:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA01464 for mobile-outgoing; Tue, 16 Dec 1997 07:15:52 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from noether.blah.org (slmel8p16.ozemail.com.au [203.22.156.176]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA01452 for ; Tue, 16 Dec 1997 07:15:43 -0800 (PST) (envelope-from ada@not-enough.bandwidth.org) Received: (from ada@localhost) by noether.blah.org (8.8.7/8.8.8) id CAA01547; Wed, 17 Dec 1997 02:14:48 +1100 (EST) From: Ada Message-Id: <199712161514.CAA01547@noether.blah.org> Subject: Re: nokia cellular In-Reply-To: from Andrew Gordon at "Dec 16, 97 11:52:53 am" To: arg@arg1.demon.co.uk (Andrew Gordon) Date: Wed, 17 Dec 1997 02:14:48 +1100 (EST) Cc: mobile@freebsd.org Reply-To: ada@bsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Tue, 16 Dec 1997, Ada wrote: > > Has anybody gotten the nokia cellular data stuff to work? > > (Any of it? I think one emulates a modem.) > > The PCMCIA card certainly works - it does indeed look just like a > modem (and if you prise open the lid on the card, you will find > a real 16C550 inside!). Which particular model is this? -- Each of us visits this Earth involuntarily, and without an invitation. For me, it is enough to wonder at the secrets. -- Albert Einstein From owner-freebsd-mobile Tue Dec 16 07:28:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA02216 for mobile-outgoing; Tue, 16 Dec 1997 07:28:07 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from lsmarso.dialup.access.net (lsmarso@lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA02179 for ; Tue, 16 Dec 1997 07:28:01 -0800 (PST) (envelope-from lsmarso@lsmarso.dialup.access.net) Received: (from lsmarso@localhost) by lsmarso.dialup.access.net (8.8.5/8.8.5) id KAA01506 for freebsd-mobile@freebsd.org; Tue, 16 Dec 1997 10:26:33 -0500 (EST) Message-ID: <19971216102627.17893@panix.com> Date: Tue, 16 Dec 1997 10:26:27 -0500 From: "Larry S. Marso" To: freebsd-mobile@freebsd.org Subject: synchronous serial pcmcia card? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm looking for a way to connect an ISDN terminal adaptor that can utilize the full 128kbps to my laptop. I can get a cheap external isdn TA, but then I'm limited by my UART 115200 serial port. Is there a synchronous pcmcia card that would permit my external ISDN TA to connect at 230400 serial speed? Or a ISDN terminal adaptor pcmcia card that supports the higher speed (many contain UART 115200 chips inside!). My preference is FreeBSD-2.2.5 or -current, without PAO. -- Larry S. Marso lsmarso@panix.com From owner-freebsd-mobile Tue Dec 16 10:02:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14068 for mobile-outgoing; Tue, 16 Dec 1997 10:02:30 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from lsmarso.dialup.access.net (lsmarso@lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14043 for ; Tue, 16 Dec 1997 10:02:22 -0800 (PST) (envelope-from lsmarso@lsmarso.dialup.access.net) Received: (from lsmarso@localhost) by lsmarso.dialup.access.net (8.8.5/8.8.5) id NAA02150 for freebsd-mobile@freebsd.org; Tue, 16 Dec 1997 13:01:04 -0500 (EST) Message-ID: <19971216130057.21831@panix.com> Date: Tue, 16 Dec 1997 13:00:57 -0500 From: "Larry S. Marso" To: freebsd-mobile@freebsd.org Subject: Re: synchronous serial pcmcia card? References: <19971216102627.17893@panix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19971216102627.17893@panix.com>; from Larry S. Marso on Tue, Dec 16, 1997 at 10:26:27AM -0500 Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry: UART 16550, verses 16650 -- is there a PCMCIA solution? -- Larry S. Marso lsmarso@panix.com On Tue, Dec 16, 1997 at 10:26:27AM -0500, Larry S. Marso wrote: > I'm looking for a way to connect an ISDN terminal adaptor that can utilize > the full 128kbps to my laptop. > > I can get a cheap external isdn TA, but then I'm limited by my UART 115200 > serial port. > > Is there a synchronous pcmcia card that would permit my external ISDN TA to > connect at 230400 serial speed? Or a ISDN terminal adaptor pcmcia card > that supports the higher speed (many contain UART 115200 chips inside!). > > My preference is FreeBSD-2.2.5 or -current, without PAO. > -- > Larry S. Marso > lsmarso@panix.com > > > From owner-freebsd-mobile Tue Dec 16 10:11:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14717 for mobile-outgoing; Tue, 16 Dec 1997 10:11:10 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14703 for ; Tue, 16 Dec 1997 10:11:03 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id SAA13277; Tue, 16 Dec 1997 18:09:45 GMT Date: Tue, 16 Dec 1997 18:09:45 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: ada@bsd.org cc: mobile@freebsd.org Subject: Re: nokia cellular In-Reply-To: <199712161514.CAA01547@noether.blah.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Dec 1997, Ada wrote: > > On Tue, 16 Dec 1997, Ada wrote: > > > Has anybody gotten the nokia cellular data stuff to work? > > > (Any of it? I think one emulates a modem.) > > > > The PCMCIA card certainly works - it does indeed look just like a > > modem (and if you prise open the lid on the card, you will find > > a real 16C550 inside!). > > Which particular model is this? The card is just labelled "Nokia Cellular Data Card" and has a model number "DTP-2". I use it with a Nokia 2110i (GSM900), but the same card also works with the 2140 phone (the GSM1800 varient of the 2110). So far as I can tell, the interface to the phone is the raw 13kbit/sec data stream, plus a separate control connection to the phone's CPU to control dialling etc. The card has its own CPU, implementing the FEC link protocol, and emulating the usual Hayes modem command set on the host side (including class1/2 fax). It also has a command-line access to send SMS messages and to interrogate the phone's store of received SMS - again, all accessed the serial port, the command "AT*C" switching into the SMS mode. My pccard.conf contains: card "Nokia Mobile Phones" "DTP-2" config 0x22 "sio2" 10 insert echo "Nokia datacard inserted" remove echo "Nokia datacard removed" From owner-freebsd-mobile Tue Dec 16 10:58:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18361 for mobile-outgoing; Tue, 16 Dec 1997 10:58:05 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA18353 for ; Tue, 16 Dec 1997 10:58:01 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA01175; Tue, 16 Dec 1997 11:57:48 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA09284; Tue, 16 Dec 1997 11:57:47 -0700 Date: Tue, 16 Dec 1997 11:57:47 -0700 Message-Id: <199712161857.LAA09284@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Larry S. Marso" Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: synchronous serial pcmcia card? In-Reply-To: <19971216130057.21831@panix.com> References: <19971216102627.17893@panix.com> <19971216130057.21831@panix.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm looking for a way to connect an ISDN terminal adaptor that can utilize > > the full 128kbps to my laptop. > > > > I can get a cheap external isdn TA, but then I'm limited by my UART 115200 > > serial port. > > > > Is there a synchronous pcmcia card that would permit my external ISDN TA to > > connect at 230400 serial speed? Or a ISDN terminal adaptor pcmcia card > > that supports the higher speed (many contain UART 115200 chips inside!). I don't know that FreeBSD's serial driver supports higher speeds than 115200, and since the PCMCIA stuff won't support it either given that it uses the same code. Nate From owner-freebsd-mobile Tue Dec 16 13:14:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA29984 for mobile-outgoing; Tue, 16 Dec 1997 13:14:28 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from mail.nomadix.com (mail.nomadix.com [205.147.49.199]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA29976 for ; Tue, 16 Dec 1997 13:14:24 -0800 (PST) (envelope-from gdicus@nomadix.com) Received: from gdicus.nomadix.com (nomad7.nomadix.com [205.147.49.207]) by mail.nomadix.com (8.8.3/8.7.2) with ESMTP id NAA12565 for ; Tue, 16 Dec 1997 13:12:38 -0800 (PST) Message-Id: <199712162112.NAA12565@mail.nomadix.com> From: "Glenn Dicus" To: "Mobile FreeBSD" Subject: pcic.c <-> pcicx.c? Date: Tue, 16 Dec 1997 11:01:16 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There are two sets of pcic code. One in /usr/src/sys/i386/isa/ directory - pcic.h and pcicx.c, and the code that is in the /usr/src/sys/pccard/ directory. Which code should I rely upon pcic.c or pcicx.c? Also, where are the procedures/functions within these files being called from? Thanks Glenn Dicus From owner-freebsd-mobile Tue Dec 16 13:50:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA02726 for mobile-outgoing; Tue, 16 Dec 1997 13:50:10 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA02714 for ; Tue, 16 Dec 1997 13:50:04 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA02269; Tue, 16 Dec 1997 14:50:03 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA10207; Tue, 16 Dec 1997 14:49:57 -0700 Date: Tue, 16 Dec 1997 14:49:57 -0700 Message-Id: <199712162149.OAA10207@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Glenn Dicus" Cc: "Mobile FreeBSD" Subject: Re: pcic.c <-> pcicx.c? In-Reply-To: <199712162112.NAA12565@mail.nomadix.com> References: <199712162112.NAA12565@mail.nomadix.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > There are two sets of pcic code. One in /usr/src/sys/i386/isa/ directory - > pcic.h and pcicx.c, and the code that is in the /usr/src/sys/pccard/ > directory. Which code should I rely upon pcic.c or pcicx.c? The code in /sys/pccard is for the GENERIC support, and the pcicx code is for the 'older' drivers for the 3Com and IBM ethernet cards, and is currently the only cards supported in teh boto floppy. > Also, where are the procedures/functions within these files being called > from? For the old code, if_zp.c and if_ze.c. For the newer code, they are being called from all over the system, but the user-land portions are in /usr/src/usr.sbin/pccard. Nate From owner-freebsd-mobile Tue Dec 16 16:05:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA13675 for mobile-outgoing; Tue, 16 Dec 1997 16:05:14 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA13664 for ; Tue, 16 Dec 1997 16:05:07 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id KAA00308; Wed, 17 Dec 1997 10:29:27 +1030 (CST) Message-Id: <199712162359.KAA00308@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ken Key cc: mobile@freebsd.org Subject: Re: APM suspend/resume and the "calltodo" timer list. In-reply-to: Your message of "Tue, 16 Dec 1997 16:05:39 CDT." <199712162105.QAA09933@duncan.cs.utk.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Dec 1997 10:29:26 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi Mike, > > you were the only person to respond, so I assume the list at large doesn't > particularly care (not a surprise). ... or they just agree and thus haven't spoken up. As a general rule, silence either means you're having mail problems, or everyone agrees with you. > I have twice experienced a problem where the X server complains that > select is failing with an EINVAL, but I thought I remember X having this > failure mode before my change. I've put the old kernel back in place > and am going to try to recreate this error in an attempt to prove it's > not the result of my hack. So I'm on hold pending this proof. Ok, please keep us informed. It sounds (so far) as though the positives outweigh the negatives. mike From owner-freebsd-mobile Tue Dec 16 16:25:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA14987 for mobile-outgoing; Tue, 16 Dec 1997 16:25:03 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA14942 for ; Tue, 16 Dec 1997 16:24:33 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id KAA00474; Wed, 17 Dec 1997 10:49:01 +1030 (CST) Message-Id: <199712170019.KAA00474@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Larry S. Marso" cc: freebsd-mobile@freebsd.org Subject: Re: synchronous serial pcmcia card? In-reply-to: Your message of "Tue, 16 Dec 1997 10:26:27 CDT." <19971216102627.17893@panix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Dec 1997 10:49:00 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm looking for a way to connect an ISDN terminal adaptor that can utilize > the full 128kbps to my laptop. Get a TA with an ethernet interface (CISCO 1000, etc.). Alternatively, depending on your laptop, you may be able to do async above 115200. mike From owner-freebsd-mobile Tue Dec 16 17:09:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA18624 for mobile-outgoing; Tue, 16 Dec 1997 17:09:14 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA18605 for ; Tue, 16 Dec 1997 17:09:05 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id LAA00786; Wed, 17 Dec 1997 11:33:18 +1030 (CST) Message-Id: <199712170103.LAA00786@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Glenn Dicus" cc: "Mobile FreeBSD" Subject: Re: pcic.c <-> pcicx.c? In-reply-to: Your message of "Tue, 16 Dec 1997 11:01:16 -0800." <199712162112.NAA12565@mail.nomadix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Dec 1997 11:33:18 +1030 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > There are two sets of pcic code. One in /usr/src/sys/i386/isa/ directory - > pcic.h and pcicx.c, and the code that is in the /usr/src/sys/pccard/ > directory. Which code should I rely upon pcic.c or pcicx.c? The stuff in i386/isa is only used by if_zp and if_ze. DO NOT use this code. > Also, where are the procedures/functions within these files being called > from? The code in sys/pccard is called out of the device entries for the pcic and card devices, and in turn calls into various drivers. mike From owner-freebsd-mobile Tue Dec 16 17:14:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19222 for mobile-outgoing; Tue, 16 Dec 1997 17:14:46 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19212 for ; Tue, 16 Dec 1997 17:14:42 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA03590; Tue, 16 Dec 1997 18:14:37 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA11050; Tue, 16 Dec 1997 18:14:35 -0700 Date: Tue, 16 Dec 1997 18:14:35 -0700 Message-Id: <199712170114.SAA11050@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Ken Key , mobile@freebsd.org Subject: Re: APM suspend/resume and the "calltodo" timer list. In-Reply-To: <199712162359.KAA00308@word.smith.net.au> References: <199712162105.QAA09933@duncan.cs.utk.edu> <199712162359.KAA00308@word.smith.net.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > you were the only person to respond, so I assume the list at large doesn't > > particularly care (not a surprise). > > ... or they just agree and thus haven't spoken up. As a general rule, > silence either means you're having mail problems, or everyone agrees > with you. FWIS, I agree with you. But, I don't have time to do anything about it. :( Nate From owner-freebsd-mobile Tue Dec 16 20:01:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA03552 for mobile-outgoing; Tue, 16 Dec 1997 20:01:38 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA03538 for ; Tue, 16 Dec 1997 20:01:25 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id BAA28353; Wed, 17 Dec 1997 01:58:56 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199712170158.BAA28353@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrew Gordon cc: ada@bsd.org, mobile@freebsd.org Subject: Re: nokia cellular In-reply-to: Your message of "Tue, 16 Dec 1997 18:09:45 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Dec 1997 01:58:56 +0000 From: Brian Somers Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Wed, 17 Dec 1997, Ada wrote: > > > > On Tue, 16 Dec 1997, Ada wrote: > > > > Has anybody gotten the nokia cellular data stuff to work? > > > > (Any of it? I think one emulates a modem.) > > > > > > The PCMCIA card certainly works - it does indeed look just like a > > > modem (and if you prise open the lid on the card, you will find > > > a real 16C550 inside!). > > > > Which particular model is this? > > The card is just labelled "Nokia Cellular Data Card" and has a model > number "DTP-2". I use it with a Nokia 2110i (GSM900), but the same card > also works with the 2140 phone (the GSM1800 varient of the 2110). > > So far as I can tell, the interface to the phone is the raw 13kbit/sec > data stream, plus a separate control connection to the phone's CPU to > control dialling etc. The card has its own CPU, implementing the FEC link > protocol, and emulating the usual Hayes modem command set on the host side > (including class1/2 fax). It also has a command-line access to send SMS > messages and to interrogate the phone's store of received SMS - again, all > accessed the serial port, the command "AT*C" switching into the SMS > mode. > > My pccard.conf contains: > > card "Nokia Mobile Phones" "DTP-2" > config 0x22 "sio2" 10 > insert echo "Nokia datacard inserted" > remove echo "Nokia datacard removed" I recently looked into getting the nk502 working as a soft-modem (you don't need the data card). Nokia say (I quote): Licence Agreement: A licence agreement is always made between the SMS SDK customer and Nokia Mobile Phones. The agreement provides Licensee the right to develop and manufacture SW and HW using the Nokia SMS SDK. The right is granted to the products of the Licensee listed in the agreement Please note: Nokia will test and approve the products before the commercial launch. ..... Further Information: If you are interested in enhancing your products or applications with mobile features, please contact us. email: cellular.partner@nmp.nokia.com This doesn't look good to me - and I never followed it up further than this. I guess we're stuck with the (rather expensive) data card :-( -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-mobile Wed Dec 17 12:34:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10878 for mobile-outgoing; Wed, 17 Dec 1997 12:34:11 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from mail.nomadix.com (mail.nomadix.com [205.147.49.199]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA10862 for ; Wed, 17 Dec 1997 12:34:06 -0800 (PST) (envelope-from gdicus@nomadix.com) Received: from gdicus.nomadix.com (nomad7.nomadix.com [205.147.49.207]) by mail.nomadix.com (8.8.3/8.7.2) with ESMTP id MAA06243; Wed, 17 Dec 1997 12:32:13 -0800 (PST) Message-Id: <199712172032.MAA06243@mail.nomadix.com> From: "Glenn Lee Dicus" To: "Nate Williams" Cc: "Mobile FreeBSD" Subject: Re: pcic.c <-> pcicx.c? Date: Wed, 17 Dec 1997 21:18:27 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1162 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk More specifically, where are "pcic_memory()" and "crdioctl()" being called from? ---------- > From: Nate Williams > To: Glenn Dicus > Cc: Mobile FreeBSD > Subject: Re: pcic.c <-> pcicx.c? > Date: Tuesday, December 16, 1997 1:49 PM > > > There are two sets of pcic code. One in /usr/src/sys/i386/isa/ directory - > > pcic.h and pcicx.c, and the code that is in the /usr/src/sys/pccard/ > > directory. Which code should I rely upon pcic.c or pcicx.c? > > The code in /sys/pccard is for the GENERIC support, and the pcicx code > is for the 'older' drivers for the 3Com and IBM ethernet cards, and is > currently the only cards supported in teh boto floppy. > > > Also, where are the procedures/functions within these files being called > > from? > > For the old code, if_zp.c and if_ze.c. For the newer code, they are > being called from all over the system, but the user-land portions are in > /usr/src/usr.sbin/pccard. > > > Nate From owner-freebsd-mobile Wed Dec 17 13:22:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA14762 for mobile-outgoing; Wed, 17 Dec 1997 13:22:25 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA14749 for ; Wed, 17 Dec 1997 13:22:19 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA10755; Wed, 17 Dec 1997 14:22:08 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA14003; Wed, 17 Dec 1997 14:22:05 -0700 Date: Wed, 17 Dec 1997 14:22:05 -0700 Message-Id: <199712172122.OAA14003@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Glenn Lee Dicus" Cc: "Nate Williams" , "Mobile FreeBSD" Subject: Re: pcic.c <-> pcicx.c? In-Reply-To: <199712172032.MAA06243@mail.nomadix.com> References: <199712172032.MAA06243@mail.nomadix.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Glenn Lee Dicus writes: > More specifically, where are "pcic_memory()" and "crdioctl()" being called > from? > > being called from all over the system, but the user-land portions are in > > /usr/src/usr.sbin/pccard. ^^^^^^^^^^^^^^^^^^^^^^^^ Nate From owner-freebsd-mobile Wed Dec 17 14:32:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA21196 for mobile-outgoing; Wed, 17 Dec 1997 14:32:24 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (ppp9.portal.net.au [202.12.71.109]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA21181 for ; Wed, 17 Dec 1997 14:32:14 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id IAA01669; Thu, 18 Dec 1997 08:56:24 +1030 (CST) Message-Id: <199712172226.IAA01669@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Glenn Lee Dicus" cc: "Nate Williams" , "Mobile FreeBSD" Subject: Re: pcic.c <-> pcicx.c? In-reply-to: Your message of "Wed, 17 Dec 1997 21:18:27 -0800." <199712172032.MAA06243@mail.nomadix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Dec 1997 08:56:23 +1030 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > More specifically, where are "pcic_memory()" and "crdioctl()" being called > from? Might I suggest you investigate global(1)? Failing that, how about find /sys -name "*.c" | xargs grep pcic_memory You'll probably find that crdioctl() is parked in the linker set for the 'crd' device; it is almost certainly its ioctl() handler, and is thus invoked when a user-space program makes an ioctl call on a /dev/crd* node. mike From owner-freebsd-mobile Wed Dec 17 21:31:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA19666 for mobile-outgoing; Wed, 17 Dec 1997 21:31:23 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from mail-gw.pacbell.net (mail-gw.pacbell.net [206.13.28.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA19659 for ; Wed, 17 Dec 1997 21:31:21 -0800 (PST) (envelope-from schluntz@pacbell.net) Received: from [206.170.30.53] (ppp-206-170-30-53.hywr01.pacbell.net [206.170.30.53]) by mail-gw.pacbell.net (8.8.8/8.7.1+antispam) with SMTP id VAA19792 for ; Wed, 17 Dec 1997 21:31:19 -0800 (PST) Message-Id: <199712180531.VAA19792@mail-gw.pacbell.net> Subject: Which Laptop do you recommend? Date: Wed, 17 Dec 97 21:34:36 -0700 x-sender: schluntz@postoffice.pacbell.net x-mailer: Claris Emailer 2.0v2, June 6, 1997 From: "Sean J. Schluntz" To: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm looking to purchase a laptop for my main system at the office and I'm wondering what the people who have experience with FreeBSD on laptops think I should get. What I need: 166-200 Pentium (mmx does not matter to me.) 64Megs RAM 800x600 Active Mat. Display 2m video RAM 2-3 gig HD Floppy & CD-ROM (both do not have to be in at the same time but it helps.) I don't want a computer that has an external floppy. PCMCIA Nic PCMCIA Modem I would really like to get a system that has a ZIP disk that will replace the floppy, but I don't know if FreeBSD supports that type of ZIP drive. Track ball (yah, I know, but I like them) or touch pad. No eraser. What am I going to be doing with it? Development, systems admin, x, and running Executor by Ardi so I can run a few Mac apps. Worst of all I need to keep it under $4000. Any suggestions? Thanks for any help! -Sean ---------------------------------------------------------------------- Sean J. Schluntz schluntz@pinpt.com Systems Engineer (408) 997-6900 x222 PinPoint Software Corporation http://www.pinpt.com From owner-freebsd-mobile Thu Dec 18 15:28:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA02487 for mobile-outgoing; Thu, 18 Dec 1997 15:28:28 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA02477 for ; Thu, 18 Dec 1997 15:28:23 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-s.isi.edu [128.9.192.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id PAA23547; Thu, 18 Dec 1997 15:28:14 -0800 (PST) Message-Id: <199712182328.PAA23547@tnt.isi.edu> To: ambrisko@whistle.com, nate@mt.sri.com cc: freebsd-mobile@FreeBSD.ORG X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Dec 1997 15:28:14 -0800 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, guys. Nate, here's a patch to -current that addresses the issue Doug raised of CL-PD6832's that are initialized to odd ports and also allows users to specify a port for their pcic other than the bios default port. Right now, this added flexibility isn't worth much, because /sys/pccard/pcic.c has its ports essentially hardwired at 0x3e0, but it seems cleaner to me anyway. It should provide a way for users with chips initialized to standard CArdBus operation to switch to 16-bit legacy mode. Doug and I (mostly Doug, since I don't see the same problems in my setup) are still poking around with his interrupts so there may be some more fixes to come, but this seems solid (and works fine on my box with PCIC_PCI_PORT defined or not (defining it to other than 0x3e0 boots, but the pcic driver doesn't find the chip). Do we need to add PCIC_PCI_PORT to the LINT config and document it? *** pcic_p.c.orig Thu Dec 18 15:07:59 1997 --- pcic_p.c Thu Dec 18 15:10:40 1997 *************** *** 135,140 **** --- 135,149 ---- u_long bcr; /* to set interrupts */ u_short io_port; /* the io_port to map this slot on */ + #ifdef PCIC_PCI_PORT + /* + * This allows builders to assign the I/O port to the legacy + * mode interface explicitly + */ + io_port = PCIC_PCI_PORT; + pci_conf_write(tag, CLPD6832_LEGACY_16BIT_IOADDR, + io_port & ~PCI_MAP_IO); + #endif /* * I think this should be a call to pci_map_port, but that * routine won't map regiaters above 0x28, and the register we From owner-freebsd-mobile Thu Dec 18 15:35:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA03103 for mobile-outgoing; Thu, 18 Dec 1997 15:35:39 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA03087 for ; Thu, 18 Dec 1997 15:35:28 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA19941; Thu, 18 Dec 1997 16:35:12 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA18248; Thu, 18 Dec 1997 16:35:00 -0700 Date: Thu, 18 Dec 1997 16:35:00 -0700 Message-Id: <199712182335.QAA18248@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: ambrisko@whistle.com, nate@mt.sri.com, freebsd-mobile@FreeBSD.ORG In-Reply-To: <199712182328.PAA23547@tnt.isi.edu> References: <199712182328.PAA23547@tnt.isi.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Nate, here's a patch to -current that addresses the issue Doug raised > of CL-PD6832's that are initialized to odd ports and also allows users > to specify a port for their pcic other than the bios default port. Ugh. I really dislike adding 'yet another' config option. > Right now, this added flexibility isn't worth much, because > /sys/pccard/pcic.c has its ports essentially hardwired at 0x3e0, but > it seems cleaner to me anyway. It should provide a way for users with > chips initialized to standard CArdBus operation to switch to 16-bit > legacy mode. So, wouldn't it be 'easier' to just hard-code the port to 0x3e0, since that's where the code expects to find it? > Doug and I (mostly Doug, since I don't see the same problems in my > setup) are still poking around with his interrupts so there may be > some more fixes to come, but this seems solid (and works fine on my > box with PCIC_PCI_PORT defined or not (defining it to other than 0x3e0 > boots, but the pcic driver doesn't find the chip). Then why allow the user to set it? Why not just hard-code it to 0x3e0 *always*? What would that break? Nate [ patch deleted ] From owner-freebsd-mobile Thu Dec 18 16:02:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA04634 for mobile-outgoing; Thu, 18 Dec 1997 16:02:57 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA04626 for ; Thu, 18 Dec 1997 16:02:52 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA20110; Thu, 18 Dec 1997 17:02:47 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA18354; Thu, 18 Dec 1997 17:02:46 -0700 Date: Thu, 18 Dec 1997 17:02:46 -0700 Message-Id: <199712190002.RAA18354@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: Nate Williams , ambrisko@whistle.com, freebsd-mobile@FreeBSD.ORG In-Reply-To: <199712182355.PAA24716@tnt.isi.edu> References: <199712182335.QAA18248@mt.sri.com> <199712182355.PAA24716@tnt.isi.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> Nate, here's a patch to -current that addresses the issue Doug raised > >> of CL-PD6832's that are initialized to odd ports and also allows users > >> to specify a port for their pcic other than the bios default port. > > > >Ugh. I really dislike adding 'yet another' config option. .... > >So, wouldn't it be 'easier' to just hard-code the port to 0x3e0, since > >that's where the code expects to find it? > > Well, it doesn't *break* anything, but it's icky. :-) But it's less icky than requiring the user to set some magic flag to get it working (which will either be set by default, so why require them to set it), or it isn't set by default so it doesn't help them when installing on their system. > I just have a > preference for configurable systems. I agree however that making a > parameter configurable that no one con configure isn't worth much > (other than as incentive to change the unconfigurable stuff). I agree, but after dealing with the PAO stuff which had zillions of different configuration parameters that needed to be set, it became a nightmare to keep *one* boot floppy that worked with everything that didn't break everyone else. > This version always maps the 6832 to the port where the pcic driver > expects it to be listening. So if we ever make the port in the pcic > driver configurable the PCI driver will follow it. (The new > dependency is to find where the pcic driver expects the card to be). Cool, I like this much better. > Here's the patch: Can I have you and Doug test it, and if things work I'll commit it to the tree. :) Nate From owner-freebsd-mobile Thu Dec 18 16:24:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA05868 for mobile-outgoing; Thu, 18 Dec 1997 16:24:37 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA05854 for ; Thu, 18 Dec 1997 16:24:30 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-s.isi.edu [128.9.192.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id PAA24716; Thu, 18 Dec 1997 15:55:49 -0800 (PST) Message-Id: <199712182355.PAA24716@tnt.isi.edu> To: Nate Williams cc: ambrisko@whistle.com, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 Dec 1997 16:35:00 MST." <199712182335.QAA18248@mt.sri.com> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Dec 1997 15:55:49 -0800 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: >> Nate, here's a patch to -current that addresses the issue Doug raised >> of CL-PD6832's that are initialized to odd ports and also allows users >> to specify a port for their pcic other than the bios default port. > >Ugh. I really dislike adding 'yet another' config option. > >> Right now, this added flexibility isn't worth much, because >> /sys/pccard/pcic.c has its ports essentially hardwired at 0x3e0, but >> it seems cleaner to me anyway. It should provide a way for users with >> chips initialized to standard CArdBus operation to switch to 16-bit >> legacy mode. > >So, wouldn't it be 'easier' to just hard-code the port to 0x3e0, since >that's where the code expects to find it? > >> Doug and I (mostly Doug, since I don't see the same problems in my >> setup) are still poking around with his interrupts so there may be >> some more fixes to come, but this seems solid (and works fine on my >> box with PCIC_PCI_PORT defined or not (defining it to other than 0x3e0 >> boots, but the pcic driver doesn't find the chip). > >Then why allow the user to set it? Why not just hard-code it to 0x3e0 >*always*? What would that break? Well, it doesn't *break* anything, but it's icky. :-) I just have a preference for configurable systems. I agree however that making a parameter configurable that no one con configure isn't worth much (other than as incentive to change the unconfigurable stuff). This version always maps the 6832 to the port where the pcic driver expects it to be listening. So if we ever make the port in the pcic driver configurable the PCI driver will follow it. (The new dependency is to find where the pcic driver expects the card to be). Here's the patch: *** pcic_p.c.orig Thu Dec 18 15:07:59 1997 --- pcic_p.c Thu Dec 18 15:45:22 1997 *************** *** 37,42 **** --- 37,43 ---- #include #include #include + #include #include #include *************** *** 135,140 **** --- 136,150 ---- u_long bcr; /* to set interrupts */ u_short io_port; /* the io_port to map this slot on */ + /* + * Some BIOS leave the legacy address uninitialized. This + * insures that the PD6832 puts itself where the driver will + * look + */ + + io_port = PCIC_INDEX_0; + pci_conf_write(tag, CLPD6832_LEGACY_16BIT_IOADDR, + io_port & ~PCI_MAP_IO); /* * I think this should be a call to pci_map_port, but that * routine won't map regiaters above 0x28, and the register we From owner-freebsd-mobile Thu Dec 18 16:30:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA06160 for mobile-outgoing; Thu, 18 Dec 1997 16:30:57 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA06153 for ; Thu, 18 Dec 1997 16:30:54 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-s.isi.edu [128.9.192.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id QAA26195; Thu, 18 Dec 1997 16:30:46 -0800 (PST) Message-Id: <199712190030.QAA26195@tnt.isi.edu> To: Nate Williams Cc: ambrisko@whistle.com, freebsd-mobile@FreeBSD.ORG In-Reply-To: Your message of "Thu, 18 Dec 1997 17:02:46 MST." <199712190002.RAA18354@mt.sri.com> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Dec 1997 16:30:46 -0800 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- On adding a config parameter, Nate Williams wrote: >I agree, but after dealing with the PAO stuff which had zillions of >different configuration parameters that needed to be set, it became a >nightmare to keep *one* boot floppy that worked with everything that >didn't break everyone else. Now *that's* a concern I hadn't thought of. This is definitely much better for boot floppies. > >> This version always maps the 6832 to the port where the pcic driver >> expects it to be listening. So if we ever make the port in the pcic >> driver configurable the PCI driver will follow it. (The new >> dependency is to find where the pcic driver expects the card to be). > >Cool, I like this much better. Good. >Can I have you and Doug test it, and if things work I'll commit it to >the tree. :) I ran it on my box, and I think Doug's hardware's sick. It works fine on my box, so count my vote. :-) - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNJnANYb4eisfQ5rpAQHMsQP+K8dyxFwJrB0wDkLO3jRfk7zWOyFYFbWJ +3bLY7aM1EOI7oVFFV/umvAs5cS7KhJH5OIQLqTCYfuE9hi+adLbiJaZ4NdZv6/L 88i8v8wrfDFM53cakKMX6H5nEpFbCsFcXSCjHw2vm9K89KiczOSmJxSgnpyCNQpH KRDsBwyRoiA= =IBy7 -----END PGP SIGNATURE----- From owner-freebsd-mobile Thu Dec 18 16:39:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA06606 for mobile-outgoing; Thu, 18 Dec 1997 16:39:13 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA06599 for ; Thu, 18 Dec 1997 16:39:10 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA20340; Thu, 18 Dec 1997 17:38:51 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA18535; Thu, 18 Dec 1997 17:38:49 -0700 Date: Thu, 18 Dec 1997 17:38:49 -0700 Message-Id: <199712190038.RAA18535@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ted Faber Cc: Nate Williams , ambrisko@whistle.com, freebsd-mobile@FreeBSD.ORG Subject: Re: PCIC I/O port patch In-Reply-To: <199712190030.QAA26195@tnt.isi.edu> References: <199712190002.RAA18354@mt.sri.com> <199712190030.QAA26195@tnt.isi.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On adding a config parameter, Nate Williams wrote: > >I agree, but after dealing with the PAO stuff which had zillions of > >different configuration parameters that needed to be set, it became a > >nightmare to keep *one* boot floppy that worked with everything that > >didn't break everyone else. > > Now *that's* a concern I hadn't thought of. This is definitely much > better for boot floppies. > > > > >> This version always maps the 6832 to the port where the pcic driver > >> expects it to be listening. So if we ever make the port in the pcic > >> driver configurable the PCI driver will follow it. (The new > >> dependency is to find where the pcic driver expects the card to be). > > > >Cool, I like this much better. > > Good. > > >Can I have you and Doug test it, and if things work I'll commit it to > >the tree. :) > > I ran it on my box, and I think Doug's hardware's sick. It works fine > on my box, so count my vote. :-) Ok, if I don't hear anything negative from Doug by the end of the weekend (or sooner if I get some free time), I'll commit it. Nate From owner-freebsd-mobile Thu Dec 18 17:43:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA10534 for mobile-outgoing; Thu, 18 Dec 1997 17:43:22 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA10526 for ; Thu, 18 Dec 1997 17:43:15 -0800 (PST) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id KAA15429; Fri, 19 Dec 1997 10:42:42 +0900 (JST) Date: Fri, 19 Dec 1997 10:42:42 +0900 (JST) Message-Id: <199712190142.KAA15429@afs.ntc.mita.keio.ac.jp> To: faber@ISI.EDU Cc: nate@mt.sri.com, ambrisko@whistle.com, freebsd-mobile@FreeBSD.ORG, hosokawa@ntc.keio.ac.jp Subject: Re: In-Reply-To: Your message of "Thu, 18 Dec 1997 15:55:49 -0800". <199712182355.PAA24716@tnt.isi.edu> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.20] 1996-12/08(Sun) Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In article <199712182355.PAA24716@tnt.isi.edu> faber@ISI.EDU writes: >> Well, it doesn't *break* anything, but it's icky. :-) I just have a >> preference for configurable systems. I agree however that making a >> parameter configurable that no one con configure isn't worth much >> (other than as incentive to change the unconfigurable stuff). I think it'll cause problems on machines that have more than two CardBus bridges, or machines that have both ISA PC-card controller and CardBus bridges. On these machines, BIOS initializes appropriate I/O port number to legacy 16-bit ioaddr register. For example, I have a machine that has both TI PCI-1130 and i82365 compatible ISA PCIC. The BIOS initializes 1130 as 0x3e0 or 0x3e4 (configurable from BIOS setup) and i82365 compatible to 0x3e2. In this case, fortunately this patch will not cause any problem because CardBus bridge is set to 0x3e0 when I configured BIOS setup, and even if FreeBSD kernel re-initializes it from 0x3e4 to 0x3e0, it'll safe if there's no other devices on 0x3e0 and 0x3e1. But if there's a machine which have ISA PC-card controller at 0x3e0 and CardBus bridge at 0x3e2, or a machine which have two CardBus bridges, it'll be the problem. I don't know such machine, but I can't say that such it does not (and will not) exist in the world. I think it'll be te better way: if (the legacy 16bit ioadder is left uninitialized, or initialized to odd value) { set it to 0x3e0 + (unit number * 2); } or if (the legacy 16bit ioadder is left uninitialized) { set it to 0x3e0 + (unit number * 2); } sp->index = legacy 16bit ioaddr; -- HOSOKAWA, Tatsumi Network Technology Center Keio University hosokawa@ntc.keio.ac.jp From owner-freebsd-mobile Thu Dec 18 17:47:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA10647 for mobile-outgoing; Thu, 18 Dec 1997 17:47:18 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA10642 for ; Thu, 18 Dec 1997 17:47:15 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA20740; Thu, 18 Dec 1997 18:47:10 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA18752; Thu, 18 Dec 1997 18:47:06 -0700 Date: Thu, 18 Dec 1997 18:47:06 -0700 Message-Id: <199712190147.SAA18752@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) Cc: faber@ISI.EDU, nate@mt.sri.com, ambrisko@whistle.com, freebsd-mobile@FreeBSD.ORG Subject: Re: In-Reply-To: <199712190142.KAA15429@afs.ntc.mita.keio.ac.jp> References: <199712182355.PAA24716@tnt.isi.edu> <199712190142.KAA15429@afs.ntc.mita.keio.ac.jp> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> Well, it doesn't *break* anything, but it's icky. :-) I just have a > >> preference for configurable systems. I agree however that making a > >> parameter configurable that no one con configure isn't worth much > >> (other than as incentive to change the unconfigurable stuff). > > I think it'll cause problems on machines that have more than two > CardBus bridges, or machines that have both ISA PC-card controller and > CardBus bridges. Good call! > I think it'll be te better way: > > if (the legacy 16bit ioadder is left uninitialized, or initialized > to odd value) { > set it to 0x3e0 + (unit number * 2); > } > > or > > if (the legacy 16bit ioadder is left uninitialized) { > set it to 0x3e0 + (unit number * 2); > } > > sp->index = legacy 16bit ioaddr; Agreed. Thanks for the feedback! Nate From owner-freebsd-mobile Fri Dec 19 08:15:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA26429 for mobile-outgoing; Fri, 19 Dec 1997 08:15:10 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA26413 for ; Fri, 19 Dec 1997 08:15:05 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id IAA06971; Fri, 19 Dec 1997 08:13:22 -0800 (PST) Received: from UNKNOWN(), claiming to be "crab.whistle.com" via SMTP by alpo.whistle.com, id smtpd006969; Fri Dec 19 08:13:21 1997 Received: (from ambrisko@localhost) by crab.whistle.com (8.8.8/8.6.12) id IAA18163; Fri, 19 Dec 1997 08:10:09 -0800 (PST) From: Doug Ambrisko Message-Id: <199712191610.IAA18163@crab.whistle.com> Subject: Re: PCIC I/O port patch In-Reply-To: <199712190038.RAA18535@mt.sri.com> from Nate Williams at "Dec 18, 97 05:38:49 pm" To: nate@mt.sri.com (Nate Williams) Date: Fri, 19 Dec 1997 08:10:09 -0800 (PST) Cc: faber@ISI.EDU, nate@mt.sri.com, ambrisko@whistle.com, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate Williams writes: | > >Can I have you and Doug test it, and if things work I'll commit it to | > >the tree. :) | > | > I ran it on my box, and I think Doug's hardware's sick. It works fine | > on my box, so count my vote. :-) | | Ok, if I don't hear anything negative from Doug by the end of the | weekend (or sooner if I get some free time), I'll commit it. I'll test it out today. Doug A. From owner-freebsd-mobile Fri Dec 19 19:13:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA14014 for mobile-outgoing; Fri, 19 Dec 1997 19:13:36 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14009 for ; Fri, 19 Dec 1997 19:13:34 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-s.isi.edu [128.9.192.240]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id TAA26364; Fri, 19 Dec 1997 19:12:56 -0800 (PST) Message-Id: <199712200312.TAA26364@tnt.isi.edu> To: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) cc: nate@mt.sri.com, ambrisko@whistle.com, freebsd-mobile@FreeBSD.ORG Subject: Re: Multiple 6832's In-reply-to: Your message of "Fri, 19 Dec 1997 10:42:42 +0900." <199712190142.KAA15429@afs.ntc.mita.keio.ac.jp> X-Url: http://www.isi.edu/~faber Mime-Version: 1.0 Content-Type: text/plain Date: Fri, 19 Dec 1997 19:12:55 -0800 From: Ted Faber Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk HOSOKAWA Tatsumi wrote: >In article <199712182355.PAA24716@tnt.isi.edu> >In this case, fortunately this patch will not cause any problem >because CardBus bridge is set to 0x3e0 when I configured BIOS setup, >and even if FreeBSD kernel re-initializes it from 0x3e4 to 0x3e0, >it'll safe if there's no other devices on 0x3e0 and 0x3e1. But if >there's a machine which have ISA PC-card controller at 0x3e0 and >CardBus bridge at 0x3e2, or a machine which have two CardBus bridges, >it'll be the problem. I don't know such machine, but I can't say that >such it does not (and will not) exist in the world. And worse, the pcic.c driver is hardwired to look at 0x3e0, so accessing both will require some modifications to that driver. > >I think it'll be te better way: > >if (the legacy 16bit ioadder is left uninitialized, or initialized > to odd value) { > set it to 0x3e0 + (unit number * 2); >} > >or > >if (the legacy 16bit ioadder is left uninitialized) { > set it to 0x3e0 + (unit number * 2); >} > >sp->index = legacy 16bit ioaddr; Looking for a badly initialized register is difficult. Which value is uninitialized, and which is just unusual? Other than that, I thinks this is a good idea. Here's a patch (to -current) that initializes each found 6832 to the next two ports in order starting at 03e0. Note that this also patches pcic_p.h to reduce the I/O ports mapped from 4 to 2. (A bug that HOSOKAWA-san's description pointed out to me.) I think this will be safe for multiple 6832's, but I can't test it. If you have two please test it and tell me. All of this runs fine on my machine, but give it more of a test before you commit it, because more changed. This should supercede the other patch. *** pcic_p.c.orig Thu Dec 18 15:07:59 1997 --- pcic_p.c Fri Dec 19 18:55:58 1997 *************** *** 37,42 **** --- 37,43 ---- #include #include #include + #include #include #include *************** *** 134,139 **** --- 135,155 ---- { u_long bcr; /* to set interrupts */ u_short io_port; /* the io_port to map this slot on */ + static int num6832 = 0; /* The number of 6832s initialized */ + + /* + * Some BIOS leave the legacy address uninitialized. This + * insures that the PD6832 puts itself where the driver will + * look. We assume that multiple 6832's should be laid out + * sequentially. We only initialize the first socket's legacy port, + * the other is a dummy. + */ + + io_port = PCIC_INDEX_0 + num6832 * CLPD6832_NUM_REGS; + if ( unit == 0 ) { + pci_conf_write(tag, CLPD6832_LEGACY_16BIT_IOADDR, + io_port & ~PCI_MAP_IO); + } /* * I think this should be a call to pci_map_port, but that *************** *** 169,174 **** --- 185,194 ---- bcr = pci_conf_read(tag, CLPD6832_BRIDGE_CONTROL); bcr |= (CLPD6832_BCR_ISA_IRQ|CLPD6832_BCR_MGMT_IRQ_ENA); pci_conf_write(tag, CLPD6832_BRIDGE_CONTROL, bcr); + + /* After initializing 2 sockets, the chip is fully configured */ + + if (unit == 1 ) num6832++; if (bootverbose) printf("CardBus: Legacy PC-card 16bit I/O address [0x%x]\n", *** pcic_p.h.orig Thu Dec 18 14:50:41 1997 --- pcic_p.h Fri Dec 19 18:21:49 1997 *************** *** 49,54 **** #define CLPD6832_BCR_MGMT_IRQ_ENA 0x08000000 #define CLPD6832_BCR_ISA_IRQ 0x00800000 #define CLPD6832_COMMAND_DEFAULTS 0x00000045 ! #define CLPD6832_NUM_REGS 4 /* End of CL-PD6832 defines */ --- 49,54 ---- #define CLPD6832_BCR_MGMT_IRQ_ENA 0x08000000 #define CLPD6832_BCR_ISA_IRQ 0x00800000 #define CLPD6832_COMMAND_DEFAULTS 0x00000045 ! #define CLPD6832_NUM_REGS 2 /* End of CL-PD6832 defines */ From owner-freebsd-mobile Sat Dec 20 07:25:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA22304 for mobile-outgoing; Sat, 20 Dec 1997 07:25:00 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA22282 for ; Sat, 20 Dec 1997 07:24:45 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.5/8.8.5) with ESMTP id PAA05147 for ; Sat, 20 Dec 1997 15:04:36 GMT Message-ID: <349BE450.789B7D5@tdx.co.uk> Date: Sat, 20 Dec 1997 15:29:20 +0000 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: mobile@freebsd.org Subject: PAO / FreeBSD 2.2.5 on HP OmniBook 800 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi All, Can somone tell me whether I stand any chance at getting FreeBSD 2.2.5-RELEASE to work on my HP OmniBook 800 laptop? I've looked at the PAO package - and this 'sort' of works - but fails - the details are below... The first problem I ran into with PAO is that unfortunately on the 800 you can't change it's Sound systems second IRQ, which is permanently on IRQ 11. The only way I can boot the disk is to disable the onboard sound system (to free up the IRQ PAO needs) - though I don't mind doing this at the moment ;-) Also, I can't get past the install part where it's detecting what's in the PCMCIA slots... I have a DLink NE-2000 Compatible PCMCIA card in either slot, and here's what happens: If I put the card in Slot 0, I get:- "Detecting Cards..." "Slot 0: Empty Slot" "Slot 1: Card "D-Link(DE-650) Assigned ed0 driver." If I put the card in Slot 1, I get:- "Detecing Cards..." "Slot 1: Card "D-Link(DE-650) Assinged ed0 driver." "Slot 2: Empty Slot" When the disk crashes it stays responsive on the ALT-2 debug screen, which shows:- DEBUG ioctl(3, TIOCCONS, NULL) = 0 (success) Card inserted, slot 1 DEBUG: Term = cons25 ed0: addres 00:80:c8:81:88:3f, type NE2000 (16 bit) I've also tried a Modem card - which again the system finds in either slot - but appears to crash when looking at the other slot. I've left the machine for 10-15 minutes with either message on the screen - and it didn't get any further... ------- According to Windows '95 (which cohabits the same machine) the system has:- 2 x Texas Instruments PCI-1130 CardBus controllers, One which Win'95 puts at IRQ 15, $cd000-$cdfff Another which Win'95 puts at IRQ 10, $ce000-cefff I've looked through your FAQ's, and have seen the TI 1130 chipset mentioned - though I must admit I've been in a hurry to get it installed (and if it finds the cards - which it does, I was thinking the Chipset must be supported? - though I now have horrible fears about the words "legacy mode" ;-) If anyone has any advice on this, or any way I can get more IRQ's to choose from on the boot disk (though I don't mind disabling sound to run FreeBSD) please let me know, Regards, Karl Pielorz From owner-freebsd-mobile Sat Dec 20 08:32:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA26168 for mobile-outgoing; Sat, 20 Dec 1997 08:32:35 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA26161 for ; Sat, 20 Dec 1997 08:32:31 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id RAA08862; Sat, 20 Dec 1997 17:26:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Karl Pielorz cc: mobile@FreeBSD.ORG Subject: Re: PAO / FreeBSD 2.2.5 on HP OmniBook 800 In-reply-to: Your message of "Sat, 20 Dec 1997 15:29:20 GMT." <349BE450.789B7D5@tdx.co.uk> Date: Sat, 20 Dec 1997 17:26:32 +0100 Message-ID: <8860.882635192@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <349BE450.789B7D5@tdx.co.uk>, Karl Pielorz writes: >Hi All, > >Can somone tell me whether I stand any chance at getting FreeBSD 2.2.5-RELEA >SE >to work on my HP OmniBook 800 laptop? This email is written from my HP800. Works fine. >I've looked at the PAO package - and this 'sort' of works - but fails - the >details are below... -Current works just fine. >The first problem I ran into with PAO is that unfortunately on the 800 you >can't change it's Sound systems second IRQ, which is permanently on IRQ 11. >The only way I can boot the disk is to disable the onboard sound system (to >free up the IRQ PAO needs) - though I don't mind doing this at the moment ;- I'm not using my sound stuff at all. That works. Remember to set the bios to "16bit cards" (or whatever it is), >not< to Cardbus. >2 x Texas Instruments PCI-1130 CardBus controllers, well, one, but it has two 'functions" one for each slot. >One which Win'95 puts at IRQ 15, $cd000-$cdfff >Another which Win'95 puts at IRQ 10, $ce000-cefff That should work. >If anyone has any advice on this, or any way I can get more IRQ's to choose >from on the boot disk (though I don't mind disabling sound to run FreeBSD) >please let me know, That worked for me. My Ether card is a IBM/National thing, which the if_ze driver recognizes, so I can boot a standard kernel. I havn't tried the PAO stuff. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-mobile Sat Dec 20 11:24:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06742 for mobile-outgoing; Sat, 20 Dec 1997 11:24:29 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA06732 for ; Sat, 20 Dec 1997 11:24:25 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA20664; Sat, 20 Dec 1997 11:24:18 -0800 Date: Sat, 20 Dec 1997 11:24:18 -0800 (PST) From: Brian Handy To: mobile@freebsd.org Subject: Mail Question Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This seems like an appropriate group for this sort of mail question, but I could be wrong. OH WELL -- tough! :-) Now that I'm laptop-empowered, I do a lot of travel and I'm never reading my email from the same place, it would be nice to get my email to follow me better. What I do now is run procmail on our server machine and sort my mail there, then read it *there* from wherever I'm at. Clearly, over a laggy network link, this sucks. What I would *like* to do is be able to pop my mail down to wherever I'm at and read it locally. But it seems like sorting my mail into the various folders sets it up so POP won't work, the mail's going into the wrong place now for this to work. I *know* you people have got to be sorting your mail...anyone offer up a pointer for how best to deal with this? (I'm POP-impaired, so if there's some feature of POP that will allow this to work for me -- be able to pop random folders down to my client -- I'd like to have a suitable RTFM directed at me...) Thanks, Brian From owner-freebsd-mobile Sat Dec 20 14:59:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20294 for mobile-outgoing; Sat, 20 Dec 1997 14:59:02 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from bh-box31337.csh.uiuc.edu (bh-box31337.csh.uiuc.edu [130.126.80.83]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20286 for ; Sat, 20 Dec 1997 14:58:49 -0800 (PST) (envelope-from bradley@dunn.org) Received: from localhost (bradley@localhost) by bh-box31337.csh.uiuc.edu (8.8.8/8.8.5) with SMTP id RAA02689; Sat, 20 Dec 1997 17:54:47 -0500 (EST) X-Authentication-Warning: bh-box31337.csh.uiuc.edu: bradley owned process doing -bs Date: Sat, 20 Dec 1997 17:54:47 -0500 (EST) From: Bradley Dunn X-Sender: bradley@bh-box31337.csh.uiuc.edu To: Brian Handy cc: mobile@freebsd.org Subject: Re: Mail Question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Dec 1997, Brian Handy wrote: > What I would *like* to do is be able to pop my mail down to wherever I'm > at and read it locally. But it seems like sorting my mail into the > various folders sets it up so POP won't work, the mail's going into the > wrong place now for this to work. IMAP was designed with mobile clients in mind. It is what you need. Pine works great with IMAP and multiple folders. Another good thing about IMAP is that you don't have to download a message if you can tell from the headers that don't want to read it. Bradley From owner-freebsd-mobile Sat Dec 20 16:53:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA26571 for mobile-outgoing; Sat, 20 Dec 1997 16:53:41 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA26566 for ; Sat, 20 Dec 1997 16:53:34 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id LAA01542; Sun, 21 Dec 1997 11:17:50 +1030 (CST) Message-Id: <199712210047.LAA01542@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Handy cc: mobile@FreeBSD.ORG Subject: Re: Mail Question In-reply-to: Your message of "Sat, 20 Dec 1997 11:24:18 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Dec 1997 11:17:49 +1030 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > What I would *like* to do is be able to pop my mail down to wherever I'm > at and read it locally. But it seems like sorting my mail into the > various folders sets it up so POP won't work, the mail's going into the > wrong place now for this to work. Sort your mail when it arrives on your laptop. POP it off the system(s) that it accumulates on. There was a major flamefest about this a little while back, with various rampant IMAP advocates shouting about how their vaporware standard was the best thing since sliced cheese. Personally I prefer a solution that works right now. 8) > I *know* you people have got to be sorting your mail...anyone offer up a > pointer for how best to deal with this? (I'm POP-impaired, so if there's > some feature of POP that will allow this to work for me -- be able to pop > random folders down to my client -- I'd like to have a suitable RTFM > directed at me...) This .fetchmailrc (and obviously fetchmail) results in mail from the remote hosts being delivered to me, locally on my laptop such that I can reply to it as thought it had come here first. I start fetchmail in the background when I log in, so it's as though mail for me was being delivered whenever I'm connected, regardless of where that might be. You would probably use procmail as your local delivery agent, rather than mail.local as I do, in order to keep your current sorting configuration. defaults proto APOP fetchall mda "/usr/libexec/mail.local %s" # Collect from smith.net.au : poll mail.smith.net.au username mike password XXXXX # Get mail from hub.freebsd.org, I'm msmith there but mike here. poll hub.freebsd.org username msmith is mike password XXXXX # mail from cain, as for hub above. poll cain.gsoft.com.au username msmith is mike password XXXXX mike From owner-freebsd-mobile Sat Dec 20 17:27:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA27957 for mobile-outgoing; Sat, 20 Dec 1997 17:27:36 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA27952 for ; Sat, 20 Dec 1997 17:27:34 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA08090; Sat, 20 Dec 1997 18:27:32 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA25503; Sat, 20 Dec 1997 18:27:32 -0700 Date: Sat, 20 Dec 1997 18:27:32 -0700 Message-Id: <199712210127.SAA25503@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brian Handy Cc: mobile@FreeBSD.ORG Subject: Re: Mail Question In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What I would *like* to do is be able to pop my mail down to wherever I'm > at and read it locally. But it seems like sorting my mail into the > various folders sets it up so POP won't work, the mail's going into the > wrong place now for this to work. Ahh, you need 'fetchmail', which gets email from your POP serer, and then sends it to you local mail agent (sendmail most likely), which will then process it correctly via your procmail setup on your laptop. I'm doing that now (although my mailhost is a SUN and not a laptop), and it works great. I'm doing it for security reason (the only incoming sendmail box allowed is our firewall), and having all our email standardized with POP has been a great maintenance boon. Nate From owner-freebsd-mobile Sat Dec 20 19:36:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA04486 for mobile-outgoing; Sat, 20 Dec 1997 19:36:33 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from bh-box31337.csh.uiuc.edu (bh-box31337.csh.uiuc.edu [130.126.80.83]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA04480 for ; Sat, 20 Dec 1997 19:36:31 -0800 (PST) (envelope-from bradley@dunn.org) Received: from localhost (bradley@localhost) by bh-box31337.csh.uiuc.edu (8.8.8/8.8.5) with SMTP id WAA02935; Sat, 20 Dec 1997 22:32:08 -0500 (EST) X-Authentication-Warning: bh-box31337.csh.uiuc.edu: bradley owned process doing -bs Date: Sat, 20 Dec 1997 22:32:07 -0500 (EST) From: Bradley Dunn X-Sender: bradley@bh-box31337.csh.uiuc.edu To: John Robert LoVerso cc: mobile@FreeBSD.ORG Subject: Re: Mail Question In-Reply-To: <199712210240.VAA06581@loverso.southborough.ma.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Dec 1997, John Robert LoVerso wrote: > > Another good thing about IMAP is that you don't have to download a message > > if you can tell from the headers that don't want to read it. > > IMAP has several features that POP doesn't. This isn't one of them. Sorry. Read RFC 2060. Specifically: 2.4. Message Texts In addition to being able to fetch the full [RFC-822] text of a message, IMAP4rev1 permits the fetching of portions of the full message text. Specifically, it is possible to fetch the [RFC-822] message header, [RFC-822] message body, a [MIME-IMB] body part, or a [MIME-IMB] header. Bradley