On 09/01/2013 18:47, Lowell Gilbert wrote:
> "Zyumbilev, Peter" writes:
>
>> On 09/01/2013 13:16, Jack Mc Lauren wrote:
>>> This is the output of pciconf -lv :
>>>
>>> vendor = 'FarSite Communications Limited'
>>> device = 'G.SHDSL Intelligent Sync Comms Card (FarSync DSL-S1)'
>
"Zyumbilev, Peter" writes:
> On 09/01/2013 13:16, Jack Mc Lauren wrote:
>> This is the output of pciconf -lv :
>>
>> vendor = 'FarSite Communications Limited'
>> device = 'G.SHDSL Intelligent Sync Comms Card (FarSync DSL-S1)'
>> class = simple comms
>>
>> So what is the
Jack Mc Lauren wrote:
> Hi all
> Sorry I ask so much cause I'm a new user to freeBSD :)
>
> Hear's the deal. How can I install a new device driver on my OS ? Please
> explain in details because of the reason I mentioned earlier :)
>
First, please understand th
On 09/01/2013 13:16, Jack Mc Lauren wrote:
> This is the output of pciconf -lv :
>
> vendor = 'FarSite Communications Limited'
> device = 'G.SHDSL Intelligent Sync Comms Card (FarSync DSL-S1)'
> class = simple comms
>
> So what is the next step ?
>
I would strongly a
o: freebsd-questions@freebsd.org
Sent: Wednesday, January 9, 2013 1:55 PM
Subject: Re: installing a new device driver
On Wed, 2013-01-09 at 02:09 -0800, Jack Mc Lauren wrote:
> How can I install a new device driver on my OS ?
I'm new to FreeBSD myself :).
Manually as root run
kldlo
On Wed, 2013-01-09 at 02:09 -0800, Jack Mc Lauren wrote:
> How can I install a new device driver on my OS ?
I'm new to FreeBSD myself :).
Manually as root run
kldload driver_name
this is something I already used myself.
To load the module automagically at startup, ed
Hi all
Sorry I ask so much cause I'm a new user to freeBSD :)
Hear's the deal. How can I install a new device driver on my OS ? Please
explain in details because of the reason I mentioned earlier :)
Thanks in advance ...
___
freebsd
Adam Vande More wrote:
>
> On Mon, Sep 10, 2012 at 2:23 PM, Robert Bonomi
> wrote:
>
> >
> > Enviorment is FreeBSD 8.3, i386
> >
> > I'm currently running a stipped-down custom kernal with all superfluous
> > devices/options removed.
> >
> > I'm trying to add the 'ndis' device back in, but whe
On Mon, Sep 10, 2012 at 2:23 PM, Robert Bonomi wrote:
>
> Enviorment is FreeBSD 8.3, i386
>
> I'm currently running a stipped-down custom kernal with all superfluous
> devices/options removed.
>
> I'm trying to add the 'ndis' device back in, but when I follow the
> directions
> on the ndis(4) man
> Date: Mon, 10 Sep 2012 15:32:30 -0400
> Subject: Re: trouble building 'ndis' device driver into stripped-down custom
> kernel.
> From: Gardner Bell
>
> On 10 September 2012 15:23, Robert Bonomi
> wrote:
> >
> > Enviorment is FreeBSD 8.3, i386
&
Enviorment is FreeBSD 8.3, i386
I'm currently running a stipped-down custom kernal with all superfluous
devices/options removed.
I'm trying to add the 'ndis' device back in, but when I follow the directions
on the ndis(4) manpage, and add:
options NDISAPI
device ndis
and try to re-com
On Jul 22, 2011, at 10:19 AM, Miller, Vincent (Rick) wrote:
> Lets say, theoretically, one wishes to replace a device driver in the FreeBSD
> media so that consequent system installs from that media built with the
> alternate driver, as opposed to the stock media driver. How
Hi,
Lets say, theoretically, one wishes to replace a device driver in the FreeBSD
media so that consequent system installs from that media built with the
alternate driver, as opposed to the stock media driver. How would one approach
this task?
==
Vincent (Rick) Miller
Systems Engineer
vmil
2010/9/24 Bob Hall :
> On Fri, Sep 24, 2010 at 07:04:06PM +0200, David DEMELIER wrote:
>> Hi folks,
>>
>> I just wonder why if_bridge(4) is prefixed by if_ for device name.
>> Every other device name like lagg(4), gif(4) are not prefixed with
>> this same one.
>
> if_bridge was based on bridge. I a
On Fri, Sep 24, 2010 at 07:04:06PM +0200, David DEMELIER wrote:
> Hi folks,
>
> I just wonder why if_bridge(4) is prefixed by if_ for device name.
> Every other device name like lagg(4), gif(4) are not prefixed with
> this same one.
if_bridge was based on bridge. I assume that when the updated if
Hi folks,
I just wonder why if_bridge(4) is prefixed by if_ for device name.
Every other device name like lagg(4), gif(4) are not prefixed with
this same one.
Is there any reason that bridge is prefixed with it ? (I don't know if
there is other device like that, but what I saw in conf/NOTES seems
Hello,
Are you aware of any this driver available? Thanks.
Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
On 8/21/09, Chris Stankevitz wrote:
> Hello,
>
> I once had a problem in linux "sometimes connecting to windows file
> sharing with CIFS is extremely slow." After too much searching, I
> discovered the problem was a buggy kernel device driver for some lame
> ether
Hello,
I once had a problem in linux "sometimes connecting to windows file
sharing with CIFS is extremely slow." After too much searching, I
discovered the problem was a buggy kernel device driver for some lame
ethernet card I bought.
Which kernel ethernet device driver works
Im running:
FreeBSD FreeSBIE.LiveCD 6.2-RELEASE FreeBSD 6.2-RELEASE #11: Wed Feb 7
16:52:42 UTC 2007
[EMAIL PROTECTED]:/usr/obj.gmv-i386/usr/src/sys/FREESBIE
i386
pciconf -l -v gives me:
[EMAIL PROTECTED]:10:0:class=0x048000 card=0x20041a7f chip=0x71301131
rev=0x01 hdr=0x00
vendor
Hi guys:
I have one urgent question to ask, please help me on this!
The following is a Makefile template for device driver with all sources
codes locating in the same directory. My question is how to write the
Makefile when the driver source codes located different directories. For
example
** please reply to [EMAIL PROTECTED] only **
Hi,
There is a working device driver of the wacom USB tablet for Linux,
at http://linuxwacom.sourceforge.net/, which supports FreeBSD only
for serial.
What I would like is support in FreeBSD for the USB tablet, more
precisely I'd
Hi,
i try to write an device driver for Accelerometer in the Thinkpad T series.
There is an Linux driver already which i ported to
FreeBSD.
So far i got a working version which returns some useful information.
What i want to know is which is the correct way to allocate io ports? I saw
some
l#ERESOURCES-MAIL:
"freebsd-arch
This list is for discussion of the FreeBSD architecture. Messages will
mostly be kept strictly technical in nature. Examples of suitable
topics are:
...
* How do we change the device driver interface to be able to use
the same drivers cleanly on many b
there is architecture handbook ,there is devleper handbook ,but is
there mailist for the driver discussion?
--
we who r about to die,salute u!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
All,
Lets supose that I am having a device that does not have support in the
FreeBSD Kernel.
How is the procedure to compile and use a device driver for FreeBSD ?
There is some place and documents to learn how to do that ?
Thanks a lot,
Giuliano
On Wed, 3 Nov 2004 20:32, Balakumar Velmurugan wrote:
> Hello,
> Is there any published book or online guide for writing
> FreeBSD device driver ?. I know a O'reily book for Linux called "Linux
> Device Drivers", is anything like that exist for Fr
Hello,
Is there any published book or online guide for writing
FreeBSD device driver ?. I know a O'reily book for Linux called "Linux
Device Drivers", is anything like that exist for FreeBSD ?.
Thanks in advance.
Bala
___
[
Richard Kaestner wrote:
Is there a helping hand to give me some advice where / how to start?
I want:
- a "pseudo device", which collects every now and then data from an external
box via serial line (/dev/cuaa1)
Box-Status and some more information shoud be readable,
whichever Commands have to be
Is there a helping hand to give me some advice where / how to start?
I want:
- a "pseudo device", which collects every now and then data from an external
box via serial line (/dev/cuaa1)
Box-Status and some more information shoud be readable,
whichever Commands have to be sent to the Box cou
I have taken several existing device driver sources and used them to
create a new device driver. However, I cannot seem to get the system to
probe for my device.
I created a device driver named vsbc which can get configured at either
0x0e0 or 0x1e0 depending on BIOS settings in a PC-104 mobo
On Fri, Jan 30, 2004 at 11:34:41AM -0600, Erik Hamilton wrote:
> I'm currently working on building a simple token ring networking scheme
> over the parallel port (/dev/ppi0) for a graduate project. The project
> itself is to be used later for educational purposes, illustrating how you
> can build a
I'm currently working on building a simple token ring networking scheme
over the parallel port (/dev/ppi0) for a graduate project. The project
itself is to be used later for educational purposes, illustrating how you
can build a network from the ground up through hardware developement,
framing, and
Hi All,
I am in the process of writing a scsi target driver on FreeBSD 4.7,
as a module. I have faced some problems like, registering the
module with CAM, probing the scsi devices connected to the host etc.,
I'm from the world of linux, wherein if I register the scsi device
driver module
100 M Mobile Connection" },
{ 0x1209, "Intel 82559ER Embedded 10/100 Ethernet" },
{ 0x1229, "Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet" },
{ 0x2449, "Intel 82801BA/CAM (ICH2/3) Pro/100 Ethernet" },
{ 0, NU
Hi,
I have found some instructions on how to patch a device driver [so as to get
an onboard network card to get picked up]. I was wondering if anyone had any
instructions on how to go about adding the patch, i have never done it
before...
[EMAIL PROTECTED]
http://lists.freebsd.org/pipermail
Has anyone had any issues with the vr device driver, or the VIA Rhine
ethernet adapter? I recently built an Internet gateway box using FreeBSD
4.8-REL. I used a 3Com 3C905C-TX board for the internal interface, and used
the internal vr interface for the external interface (to the cable modem). I
I've got a dual serial port PCI card. I've added the pcuc device to my
kernel, and it's detected like thsi (from dmesg):
puc0: port 0xfce0-0xfcff irq 11 at device 6.0 on pci0
sio4: type 16550A
sio5: type 16550A
Which looks good so afre.
However, I don't know how to get these assinged, so that
about it by email.
Regarding to my USB device, it is a mp3 player based on compact flash.
I would like to create a char device driver to implement the classical
read/write/open/close/ioctl syscalls.
I am still reading and searching for information to create the driver but
I think that there
On Wed, Mar 26, 2003 at 06:57:19PM +0800, Katinka Mills wrote:
>
> May I ask what USB device you are writing for, as I am looking at developing
> a USB interface for UPS support so NUT can use my UPS (ATM I can only use it
> under Linux ikkies)So we may be able to share knowledge and reach both ou
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of David Rio
> Sent: Wednesday, 26 March 2003 6:37 PM
> To: taxman
> Cc: [EMAIL PROTECTED]
> Subject: Re: usb device driver skeleton?
>
>
> On Tue, Mar 25, 2003 at 08:48:03
On Tue, Mar 25, 2003 at 08:48:03PM -0500, taxman wrote:
> On Tuesday 25 March 2003 12:15 pm, David Rio wrote:
> > Hi all:
> >
> > I want to port a linux device driver that I did to *BSD. I would
>
> That would be great.
Yes.. We have to help BSD movement, if not linu
On Tuesday 25 March 2003 12:15 pm, David Rio wrote:
> Hi all:
>
> I want to port a linux device driver that I did to *BSD. I would
That would be great.
> like to know if there is some source of information to develope
> usb device drivers in freebsd. Handbook talks about usb i
Hi all:
I want to port a linux device driver that I did to *BSD. I would
like to know if there is some source of information to develope
usb device drivers in freebsd. Handbook talks about usb in general,
an about device drivers but not about usb device drivers. My last
option is to read some
44 matches
Mail list logo
