Re: D-Link DSL210 USB in FreeBSD 6.x ?
2006/6/5, Bachilo Dmitry <[EMAIL PROTECTED]>: В сообщении от Понедельник 05 июня 2006 10:04 Roberto Lima написал(a): > Hi all, > How do I make to runs the DLINK DSL210 USB in my freebsd? I tried this > with Linux, and I not have success .. > > Anyone can help me? > > Thanks and sorry for my bad english. > > Roberto. Is sat a wireless network USB adapter? If so, then there is no way to run USB Wi_Fi in FreeBSD nor in Linux, only PCI or PCMCIA adapters are supported for now as far as I know. Even with Windows native drivers. But no USB... Actually, some USB wireless adapters are supported via ural(4). If the adapter is made of Ralink USB chipset, it might just work by kldloading if_ural.ko. However, I've experienced frequent loss of connection during cvsup with if_ural, on modest-heavy traffic. > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- С уважением, Бачило Дмитрий Руководитель отдела системной интеграции ООО "Компания СоЛинк" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Regards, Sangwoo Shim ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvi for serious hacking
2005/10/17, Marc Fonvieille <[EMAIL PROTECTED]>: > On Mon, Oct 17, 2005 at 02:46:56AM +0400, Oleg Petrov wrote: > > Hello, FreeBSD people. > > > > First thing to mention is that I'm very experienced Emacs user. I was using > > it > > for 4-5 years or so. But sometime ago i began to feel myself so > > uncomfortable > > with it for some reasons: first, i use many different systems and emacs > > isn't > > default application for FreeBSD or any other *BSD\Linux distribution. > > Second, > > remote machines aren't powerful enough to start Emacs fast. I tried many > > small > > Emacs clones like jed, joe, uemacs and several others i just can't remember. > > But for different reasons i disliked all of them. Later I noticed default > > `nvi' editor, that has some nice features: it comes with FreeBSD by default > > and according to documentation it has powerful editing mechanism. > > > > So, my question goes to all FreeBSD hackers who uses `nvi' as their general > > editor. Is it possible to do serious hacking with it? More accurate: > > > > I'd say "s/nvi/vim" (see http://www.vim.org/) if you want to really do > everything with your Vi. Actually the first thing that I do after minimal installing of new system is to install vim from the ports tree. (in fact, installing cvsup, of course :-) I remember once upon a time someone (david?) made a suggestion that nvi in our tree should be changed to vim-lite(or something.) I'm tend to agree with that.. (Although vim is GPL'd, nvi is in the src/contrib anyway..) Regards, Sangwoo Shim > > Marc > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: malloc() in kernel and increasing mbuf and cluster size
2005/10/17, kamal kc <[EMAIL PROTECTED]>: > > > sys/malloc.h has function prototypes for malloc() > > > kern/kern_malloc.c defines the malloc() > > > > > > the malloc() definition is > > > > > > void * > > > malloc(size, type, flags) > > > unsigned long size; > > > struct malloc_type *type; > > > int flags; > > > > > > i understand the size and flags but what shall i > > > do with the malloc_type. > > > > man 9 malloc :-) > > > > i saw the man pages. > > it says to use malloc_type via > > MALLOC_DEFINE(type,shortdesc,longdesc) > MALLOC_DECLARE(type) > > the man pages use M_FOOBUF(where did it come from ??) > in the field type. > > Now how should i code it. > > struct malloc_type mytype; > mytype=MALLOC_DEFINE(.,"mybuffers","mybuffers"); > > what should i put in the type field ?? > > thanks in advance, > kamal malloc type is defined for some kind of statistics/trackings. If you define some specific malloc types for your module/driver etc., you can track the memory usage more accurately. For example, if you do vmstat -m you can see how much memories are used for specific allocations by looking at type field. Regards, Sangwoo Shim > > > > > > > > > __ > Yahoo! Music Unlimited > Access over 1 million songs. Try it free. > http://music.yahoo.com/unlimited/ > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Driver Development Books?
2005/10/12, Scott Long <[EMAIL PROTECTED]>: > Pete wrote: > > Hello, > >I have what may seem to be a silly question, but I cannot find any > > other decent resources on the web. >.< The problem that I am having > > right now is > > that I have a fairly nice graphics card which, for the moment is only > > supported on Windows Operating systems, and old 2.4 Linux kernels. So > > far there has > > not been much positive outlook in porting the drivers to *BSD or any of > > the 2.6 kernels that I know of, let alone 64-bit drivers for non-Win OSes. > > > > So I guess that makes my question fairly simple then; I know that driver > > code is written in C (which I am learning currently) but thats about all > > I know. I'm probably > > not far off when I say that I need more to go on. Yet, from looking at > > Amazon.com I have not been able to find any books on writing driver > > code, which is really > > frustrating. > > > > One of my security related books, Rootkits, tells me about how to write > > drivers for a completely different reason so I know a bit more about how > > they work but again > > the code involved does not interface hardware to the OS, just injects a > > custom application. The other tool that I will probably use is Jungo, > > which is a nice-looking > > application which automates a skeletal version of the driver you need, > > but again, I would not know how to fill it out. > > > > Any help is appreciated. > > > > -Pete > > > > There are indeed no books that I know of on the subject of writing > drivers for any *BSD, let alone FreeBSD. [snip] For me, following book was quite helpful: Embedded FreeBSD cookbook, by Paul Cevoli ISBN: 1589950046 It tells about basic kernel data structure for driver writing. One of the best aspect of this book is that it shows you real code for real device (a simple PCI device). Moreover, it was quite easy to read. Although it focuses on FreeBSD 4.X. For those who want some _introduction_ for the FreeBSD driver writing, I would like to recommend this. Regard, Sangwoo Shim ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
