04-13-2014
You can always try to build a kernel with it, but I doubt it will work. If it did, it'd be part of the GENERIC config.
Also, note that the bktr driver appears to be an i2c master. You'd need iic(4) on hppa (I'm not familiar with the architecture, just mentioning it).
Regards,
Alister
8 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
hello ppl,
me and a friend, tired of waiting for nvidia to help the community creating a nvidia driver for bsd, decided to make yet another petition to deliver nvidia as a way of protest. didn't we buy a nvidia card just like a common windows or linux user? didn't we pay for it? so, why... (0 Replies)
Discussion started by: crashnburn
0 Replies
2. UNIX for Advanced & Expert Users
I am looking for a guide on how to program for either the Linux or FreeBSD (includes 4.4BSD, NetBSD or OpenBSD) kernel. I would prefer to learn how to write device drivers, but anything would help.
If you know, please email me at *removed* or leave a post here
Regards,
Farhan (0 Replies)
Discussion started by: Farhan
0 Replies
3. Linux
I recently started working with Linux and wrote my first device driver for a hardware chip controlled by a host CPU running Linux 2.6.x kernel.
1. The user space process makes an IOCTL call with pointer to a user memory buffer.
2. The kernel device driver in the big switch-case of IOCTL,... (1 Reply)
Discussion started by: agaurav
1 Replies
4. BSD
Hi
I need the BSD core (kernel) operating system
Please let me download link
I'm from Iran
Please help me
Thank you very much (1 Reply)
Discussion started by: sepadl71
1 Replies
5. BSD
Hi. I am thinking to create an OS. I don't want to use linux kernel. I want to use BSD Kernel and this also means that because will be on UFS, I cannot use Gparted.
This are my 2 questions.
1) Where can I download BSD Kernel.
2) Witch is the tool to create the partitions. (I think is gpart but I... (1 Reply)
Discussion started by: snuffell
1 Replies
6. Fedora
I have been reading prep questions for my second unix academy exam, and there's a nuance, I'm not sure I understand it correctly.
I've been under impression from my readings of book by Evi Nemeth and from unix academy DVDs I've been watching, that kernel's modules are drivers. I think of it, as... (25 Replies)
Discussion started by: newlinuxuser1
25 Replies
7. Hardware
In general terms what are the differences platform driver,codec driver and Machine driver? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
8. Ubuntu
I'm a beginner to the Linux programming and trying my hands on some device driver examples while practising. The below code (a trimmed down version of tiny_tty.c from ldd3 book) loads perfectly using insmod and I'm able to see it in /proc/tty/drivers , /proc/modules and device nodes are getting... (1 Reply)
Discussion started by: diwsdiwa
1 Replies
LEARN ABOUT FREEBSD
gpioiic
GPIOIIC(4) BSD Kernel Interfaces Manual GPIOIIC(4)
NAME
gpioiic -- GPIO I2C bit-banging device driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device gpio
device gpioiic
device iic
device iicbb
device iicbus
DESCRIPTION
The gpioiic driver provides an IIC bit-banging interface using two GPIO pins for the SCL and SDA on the gpiobus. gpioiic implements an open
collector kind of output, as recommended by the standard, when driving the pins on the gpiobus, i.e, they are never switched to the logical
value of '1', or they are '0' or simply open (Hi-Z/tri-state). So the pullup resistors are required so gpioiic can work.
On a device.hints(5) based system, like MIPS, these values are configurable for the gpioiic:
hint.gpioiic.%d.at The gpiobus you are attaching to. Normally just gpiobus0.
hint.gpioiic.%d.pins This is a bitmask of the pins on the gpiobus that are to be used for SCLOCK and SDATA from the GPIO IIC bit-banging
bus. To configure pin 0 and 7, use the bitmask of 0b10000001 and convert it to a hexadecimal value of 0x0081. Please
note that this mask should only ever have two bits set (any other bits - i.e., pins - will be ignored).
hint.gpioiic.%d.scl Indicates which bit in the hint.gpioiic.%d.pins should be used as the SCLOCK source. Optional, defaults to 0.
hint.gpioiic.%d.sda Indicates which bit in the hint.gpioiic.%d.pins should be used as the SDATA source. Optional, defaults to 1.
On a FDT(4) based system, like ARM, the DTS part for a gpioiic device usually looks like:
gpio: gpio {
gpio-controller;
...
gpioiic0 {
compatible = "gpioiic";
/*
* Attach to GPIO pins 21 and 22. Set them
* initially as inputs.
*/
gpios = <&gpio 21 1 0
&gpio 22 1 0>;
scl = <0>; /* GPIO pin 21 - optional */
sda = <1>; /* GPIO pin 22 - optional */
/* This is an example of a gpioiic child. */
gpioiic-child0 {
compatible = "lm75";
i2c-address = <0x4f>;
};
};
};
Where:
compatible Should always be set to "gpioiic".
gpios The gpios property indicates which GPIO pins should be used for SCLOCK and SDATA on the GPIO IIC bit-banging bus. For more
details about the gpios property, please consult /usr/src/sys/boot/fdt/dts/bindings-gpio.txt.
scl The scl option indicates which bit in the gpios should be used as the SCLOCK source. Optional, defaults to 0.
sda The sda option indicates which bit in the gpios should be used as the SDATA source. Optional, defaults to 1.
SEE ALSO
fdt(4), gpio(4), gpioled(4), iic(4), iicbb(4), iicbus(4)
HISTORY
The gpioiic manual page first appeared in FreeBSD 10.1.
AUTHORS
This manual page was written by Luiz Otavio O Souza.
BSD
May 14, 2014 BSD