Re: Memory Mapping -2
Hi, I am trying to write a PCI ethernet driver for FreeBSD 3.4 release. Will you folks please give up and move to 4.x? 3.x is *dead*. 8) I have some questions 1. How can I convert physical address to virtual address . What I want is to read the physical address from the device register and to copy it to host memory. From my earlier post I found that I can use vtopys macro to convert virtual to physical address. Now I want to do the reverse. You don't do it like this. Firstly, you shouldn't use vtophys, you should be using busdma. Secondly, a physical page can appear in more than one virtual location. Typically your ethernet hardware will have a descriptor associated with each buffer, and you need to use the descriptor to backtrack to your control structure which references the actual virtual address you care about. 2. What are things should I do if I want the driver to work on alpha platform also. a) Move to 4.x b) Use the busspace and busdma interfaces -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IEEE1394 driver system for -current
I announced IEEE1394 device driver on FREENIX'99 (sorry not on '00). I have caught up -current version at this time. The latest -current driver patch can be found at: ftp://ftp.uec.ac.jp/pub/firewire/beta/ I hope you success to make a kernel on your source tree. Thanks again for the reminder about this. I've taken some time to play a little with the code and some hardware, and I have some comments on the code and what needs to be changed before it would be suitable for committing. The driver function is still limited and may include many bugs since the driver has been used for specific purrposes, e.g., the driver have not supported SCSI (CAM) storage on IEEE1394 and not been complient to loadable kernel module. However, I think it is better to merge -current on this time and maintain on it compared with taking a effort in independent. Let me know what shall I do to merge my code. There are several things that need to be fixed. I'm not going to be nice about the code, because it needs some major work before it is ready, but I do think that it is worth using your code (and your skills) in some form. 1) The code is very messy. This makes it hard to read. It needs to be reformatted before committing to reduce whitespace/style changes afterwards. 2) There are a lot of "magic numbers" (numeric values for registers and so forth) rather than defined constants. This makes it hard to work out what parts of the code are doing. 3) The code lacks structure. There are some very clear divisions that should be made between the various components in the 1394 stack, and these are not being made. Fixing this will involve moving a lot of code around, and should be done before the code is committed. 1394 can be looked at as being quite similar to USB (the predominant interface model is OHCI, also used for USB). The obvious software components are: a) Host adapter driver (eg. TI Lynx, NEC, Adaptec, etc.) b) Generic 1394 layer c) Peripheral/protocol driver layer (eg. DV, CAM shim, etc) c') Layered peripheral/protocol driver layer The interface between layers a) and b), and between layers b) and c) and between layers c) and c') should all be clearly defined. Using newbus and defining these interactions in terms of parent-child relationships and bus methods will make this very easy. Having said so many cruel things about your code, it's clear that you've spent a lot of time making your stack work, and during that time you must have accumulated a lot of experience with these peripherals. I understand that Warner has proposed you be granted CVS commit access in order to work on your code in the FreeBSD CVS repository, and I'm in favour of this. I would, however, like to see the above issues addressed before the initial import. One option that you might want to consider is working with Bill Paul on the cleanup and restructuring process. Bill has a lot of experience with network-like peripherals, and with the way in which we like things to be done. In combination with your experience with 1394 in general, I think this would result in some very good and useful code. I've already spoken to Bill about this, and he seemed interested. (Apologies if I'm dumping you in it here, pal. 8) In summary, then, I would encourage you to consider the points above, and engage in some discussion (either on the -arch list or on a new freebsd-1394 list) about how to go about reorganising and cleaning up your code ready for committing as soon as practical. Regards, -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Size limits for kld's?
Unfortunately, while the open and close functions I wrote are called
correctly, the ioctl function is never called. A call to ioctl(filehdl,
PLEX86_IOCTL, int) returns an error, and a perror("ioctl") prints
"ioctl: Bad Address." I know that the ioctl number is correct, and it
was defined with the proper _IO* macro. The file handle also opens just
fine, as the printf's in my open function are executed and show on the
console. AFAIK, that error would be caused by an EFAULT being returned
somewhere in the chain.
What I'm asking is, what would cause some of the functions referenced by
my driver's cdevsw to not be able to be called? Are there size limits
on functions in a kld? Or a limit on the total size of a kld?
Nope. But the third argument to ioctl() is typically the *address* of
your integer parameter.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: sysctl from kernel
In message [EMAIL PROTECTED], Maxime Henrion writes: Thanks for your help ! If someone would be kind enough to answer them, I have a few other questions. I'm currently trying to modify sysctl_kern_proc() function in src/sys/kern/kern_proc.c First: look at sysctl(3) sysctl can read and set variables, so you pass it the "new" value and a buffer for the "old" value. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: perlcc in current - xs_init and boot_DynaLoader
If i do a perlcc test.pl i get the folllowing , in CURRENT ? Must i define something beforehand, or is it broken ? I'll take a look... Looks like perl brokenness. The missing boot_DynaLoader is in DynaLoader.a, but there is no way of linking it in. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
SYN flood prevention methods
Hi, I know this is an old topic but I don't seem to find answers to my questions in the mailing list archives. I'm wondering why FreeBSD did not implement the SYN cookies method that is currently implemented in Linux? To my best understanding, SYN cookie seems to be a better method against SYS flood than the random drop method. It seems both OpenBSD and FreeBSD have implemented the random drop method. I guess there are must be some "bad things" about SYN cookies that I don't know about. Also, I was looking at the netinet/ code this morning but was not able to find how the seq backlog queue is created/defined. Thanks! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SYN flood prevention methods
FengYue wrote: Hi, I know this is an old topic but I don't seem to find answers to my questions in the mailing list archives. I'm wondering why FreeBSD did not implement the SYN cookies method that is currently implemented in Linux? To my best understanding, SYN cookie seems to be a better method against SYS flood than the random drop method. It seems both OpenBSD and FreeBSD have implemented the random drop method. I guess there are must be some "bad things" about SYN cookies that I don't know about. A quick search of the net, hackers, and security mail lists turned up a number of hits for "syn cookie", including several with URL references to weaknesses in the scheme. http://www.FreeBSD.org/cgi/search.cgi?words=syn+cookiemax=50sort=scoresource=freebsd-securitysource=freebsd-hackerssource=freebsd-net -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach)
are there plans to replace FreeBSD's libc with GNU glibc in the near or medium future? Thanks for all your replies. I perfectly understand the reasons for avoiding GNU copylefted code like glibc in FreeBSD. Using the Hurd/Mach as kernel replacement for FreeBSD would indeed require adding the syscall emulation feature like in Lites/RT-Mach, linking against FreeBSD's libc and adding missing functionality as stubs. I just hoped it would be a bit easier ;-) BTW, I don't have any problems with the FreeBSD kernel itself or its libc. They are excellent and I'm using them both at home and exclusively for mission critical applications. Keep up the good work! -Farid. -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | [EMAIL PROTECTED] - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach)
are there plans to replace FreeBSD's libc with GNU glibc in the near or medium future? Linux moved also from it's own libc5 to glibc (=libc6) some time ago and it may be useful to do the same in FreeBSD too. Nope. The license for glibc is not one we'd want to use for such a core component (which is less optional than, say, grep) nor does our libc lack for the kinds of features which would make switching necessary. Those wishing to play with the HURD under FreeBSD can simply add glibc to the list of components they need to bring over; they needs of the few do not outweigh the needs of the many in this case. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fbsd box acting as a wavelan BS
Eric Kozowski wrote: On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: Hi all, Has anyone managed to configure a fbsd box as a Wavelan BS ? yes it's easy. which wavelan card are you using? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message Wavelan Orinoco...Silver (with the ISA bridge) I would like to know how but ...do you really mean that the fbsd box is acting a base station with the wavelan card in *infrastructure* mode or do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc mode is very easy...what I want is to have the fbsd base station act as an access point where _many_ clients can associatenot just one so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to peer connection ) or infrastructure mode...??? If it works in ad-hoc mode the PCF and DCF functions are not really happening...which is what a BS is all about... Don't you agree? (or anyone else) Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Auto DMA vs. Manual DMA Settings... FBSD 3.51
Hi Doug... Actually, it is a proper UDMA66 cable (so agrees the Promise UDMA66 controller I was playing with a while back). But ... I'm not looking for UDMA66 speeds, like I mentioned - the motherboard only supports UDMA33 anyways. With a tip from another reply, I found this on Maxtor's website: (although my ASUS board is much newer than Oct 98, it's a start) Overview: Some older Ultra DMA 33 motherboards with older BIOS' (revision date 10/28/98 and older) have exhibited compatibility issues with Ultra DMA/66/100 drives. The symptom manifests itself as a system hangs at boot, and performance problems. On some motherboards the system does not properly check the UDMA setting returned by the drive. The end result is that the motherboard attempts to set itself up in an unsupported mode. These issues arise because of a bug in the system's BIOS, NOT a problem with the Maxtor hard drive. Some System's will also have performance problems due to the controller chipset. To eliminate this problem, Maxtor has developed the UDMAUPDT.EXE ... Jamie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Doug White Sent: Friday, August 25, 2000 10:57 pm To: Jamie Hermans Cc: [EMAIL PROTECTED] Subject: Re: Auto DMA vs. Manual DMA Settings... FBSD 3.51 It may be that: a) your cable is damaged; b) your system is too noisy; c) your disks proclaim UDMA capability but can't actually deliver it. I'd suggest upgrading to a proper DMA66 cable and see if that helps. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fbsd box acting as a wavelan BS
Last I checked the wi driver will not do IBSS and says so in the documentation. I also tried it and couldn't get anywhere. Would be nice. Even better would be to use the algos in their office router stuff. We're looking at that now. We currently use a fbsd box to connect the Internet to a WavePointII on one frequency and then on a second frequency we connect multipoint users with fbsd boxes. Works very well although the WavePointII has to be monitored continuously. Bandwidth varies from 600 kbps to about 3000 kbps. Jim Flowers [EMAIL PROTECTED] #4 ranked ISP on C|NET #1 in Ohio On Sat, 26 Aug 2000, Theo PAGTZIS wrote: Eric Kozowski wrote: On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: Hi all, Has anyone managed to configure a fbsd box as a Wavelan BS ? yes it's easy. which wavelan card are you using? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message Wavelan Orinoco...Silver (with the ISA bridge) I would like to know how but ...do you really mean that the fbsd box is acting a base station with the wavelan card in *infrastructure* mode or do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc mode is very easy...what I want is to have the fbsd base station act as an access point where _many_ clients can associatenot just one so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to peer connection ) or infrastructure mode...??? If it works in ad-hoc mode the PCF and DCF functions are not really happening...which is what a BS is all about... Don't you agree? (or anyone else) Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fbsd box acting as a wavelan BS
Jim Flowers wrote: Last I checked the wi driver will not do IBSS and says so in the documentation. I also tried it and couldn't get anywhere. Would be nice. Jim, do you mean Bill's driver doesn't do adhoc mode...? IBSS is independent BSS which is adhoc mode...did you mean to say BSS ?? Even better would be to use the algos in their office router stuff. We're looking at that now. Couldn't agree more... We currently use a fbsd box to connect the Internet to a WavePointII on one frequency and then on a second frequency we connect multipoint users with fbsd boxes. wait a minute...a single WPII bridge is connected behind a fbsd router box.fine...now one freq is to act as a portal for the ...Internet?? and the other is to act as an AP for the nodes... but the BS can operate in a single freq...cannot switch between different frequencies (unless you set it manually but this is a different cell altogether...from the portal cell to Inet..) something is not quite right here...could you explain a little? Works very well although the WavePointII has to be monitored continuously. Bandwidth varies from 600 kbps to about 3000 kbps. why does the WPII have to be monitored? In any case the AP function is not effected in the fbsd box but on lucent's bridge...well that is what I am doingfor the moment... Do you have any code that is checking out the office router algos? I would appreciate a peek :) Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fbsd box acting as a wavelan BS
On Sat, Aug 26, 2000 at 07:00:55PM +0100, Theo PAGTZIS wrote: Eric Kozowski wrote: On Thu, Aug 24, 2000 at 05:16:16PM +0100, Theo PAGTZIS wrote: Hi all, Has anyone managed to configure a fbsd box as a Wavelan BS ? yes it's easy. which wavelan card are you using? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message Wavelan Orinoco...Silver (with the ISA bridge) I would like to know how but ...do you really mean that the fbsd box is acting a base station with the wavelan card in *infrastructure* mode or do you mean that the box operates in ad-hoc (peer to peer ) mode. Adhoc mode is very easy...what I want is to have the fbsd base station act as an access point where _many_ clients can associatenot just one so which of the two does the fbsd "wavelan BS" do ...adhoc mode (peer to peer connection ) or infrastructure mode...??? a wavelan accesspoint operates in infrastructe mode, which means that the client can only talk to the base station/accesspoint. ad-hoc means clients can contact each other directly. the wi driver supports both modes. i'm running my wavelan gold card in BSS mode to an apple airport base station. If it works in ad-hoc mode the PCF and DCF functions are not really happening...which is what a BS is all about... not sure what you mean by pcf and dcf. i do know that power saving mode will not work in ad-hoc mode. Don't you agree? (or anyone else) with what? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
UNSUBSCRIBE REMOVE
On 22 Aug 2000, at 9:47, freebsd-hackers-digest wrote: freebsd-hackers-digestTuesday, August 22 2000Volume 04 : Number 927 In this issue: [PATCH] 3-button microsoft-type serial mouse Updated driver for Mylex 160/170/352/2000/3000 controllers UNSUBSCRIBE Re: quotas and file creditentials Re: [PATCH] 3-button microsoft-type serial mouse Re: quotacheck on a live filesystem; safe? (fwd) Re: freebsd and non-preemtive threads Re: freebsd and non-preemtive threads Memory Mapping Re: Memory Mapping Advanced OS Questions only you can answer... Re: Advanced OS Questions only you can answer... Re: Advanced OS Questions only you can answer... Re: Advanced OS Questions only you can answer... IBM ServerRaid Re: Advanced OS Questions only you can answer... kernel debugging on 4.1-release -- Date: Mon, 21 Aug 2000 19:37:03 +0300 From: Ruslan Ermilov [EMAIL PROTECTED] Subject: [PATCH] 3-button microsoft-type serial mouse - --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Hi! I have a 3-button microsoft-type serial mouse (I do not know the vendor, only FCC ID if needed) which generates the `middle button down' event as previous `button down/up' event (any). Attached are: 1. the script(1) output of unmodified moused(8) with comments on events. 2. the patch that makes my mouse's 3rd button work. Cheers, - -- Ruslan ErmilovOracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED]FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.orgThe Power To Serve http://www.oracle.com Enabling The Information Age - --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="moused.script" Script started on Mon Aug 21 18:55:26 2000 perl# moused -d -f -p /dev/cuaa1 moused: PnP COM device rev 1.0 probe... moused: modem status 03 moused: alternate probe... moused: pnpwakeup2(): valid response. moused: M 4d moused: non-PnP mouse 'M' moused: PnP serial mouse: 'PNP0F01' '' '' moused: proto params: 40 40 40 00 3 dc 00 moused: port: /dev/cuaa1 interface: serial type: microsoft model: generic Left button pressed: moused: received char 0x60 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 60,0,0,0,0,0,0,0 moused: tv: 966873379 603859 moused: : 966873377 3320 moused: flags:0001 buttons:0001 obuttons: moused: activity : buttons 0x0001 dx 0 dy 0 dz 0 moused: mstate[0]-count:1 moused: button 1 count 1 Left button released: moused: received char 0x40 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 moused: tv: 966873380 693550 moused: flags:0001 buttons: obuttons:0001 moused: activity : buttons 0x dx 0 dy 0 dz 0 moused: mstate[0]-count:1 moused: button 1 count 0 Right button pressed: moused: received char 0x50 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 50,0,0,0,0,0,0,0 moused: tv: 966873382 523875 moused: : 966873377 3320 moused: flags:0004 buttons:0004 obuttons: moused: activity : buttons 0x0004 dx 0 dy 0 dz 0 moused: mstate[2]-count:1 moused: button 3 count 1 Right button released: moused: received char 0x40 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 moused: tv: 966873383 493579 moused: flags:0004 buttons: obuttons:0004 moused: activity : buttons 0x dx 0 dy 0 dz 0 moused: mstate[2]-count:1 moused: button 3 count 0 Middle button pressed: moused: received char 0x40 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 Middle button released: moused: received char 0x40 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 3) 40,0,0,0,0,0,0,0 perl# exit Script done on Mon Aug 21 18:56:28 2000 - --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="moused.c.patch" Index: moused.c === RCS file: /home/ncvs/src/usr.sbin/moused/moused.c,v retrieving revision 1.45 diff -u -p -r1.45 moused.c - --- moused.c2000/04/21 14:20:25 1.45 +++ moused.c 2000/08/21 16:09:44 @@ -1660,8 +1660,7 @@ r_protocol(u_char rBuf, mousestatus_t *a ? MOUSE_BUTTON2DOWN : butmapmss[(pBuf[0] MOUSE_MSS_BUTTONS) 4]; else - - act-button |= (act-obutton MOUSE_BUTTON2DOWN) - - | butmapmss[(pBuf[0] MOUSE_MSS_BUTTONS) 4]; + act-button |= butmapmss[(pBuf[0] MOUSE_MSS_BUTTONS) 4];
Re: UNSUBSCRIBE REMOVE
On Saturday, August 26, 2000, [EMAIL PROTECTED] wrote: [2,640 lines removed] ... and this was at the bottom of the message you quoted: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message At the very least, don't just mail a whole day's worth of data back to the list with "UNSUBSCRIBE REMOVE" affixed to the subject line. Don't you know how much bandwidth and money you're wasting for people who have to pay for the amount of data they download? I'm sending this to the list because hopefully someone else reading it and wanting to unsubscribe won't make the same mistake. -- |Chris Costello [EMAIL PROTECTED] |Justify my text? I'm sorry but it has no excuse. `- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
