teicors
Posts: 4
Joined: Thu Jul 26, 2012 11:13 pm

Re: kernel patch for Dallas 1-wire interface

Sun Aug 05, 2012 1:41 pm

Frank Buss wrote:I've tested the GPIO one-wire implementation in the Linux kernel. This is the Linux kernel patch:

https://github.com/FrankBuss/linux-1/tree/rpi-w1
Hi Frank,
I try to enclose your code into the latest kernel to use also an audio client while reading the DS18B20. Comparing the git for the 3.2.18 and your lernel, it seems the all the mofications at the code are only few lines. Here's the diff

Code: Select all

angelo@hp630:~/Software/raspberrypi$ diff -r  linuxrpi-3.2.18 linuxrpi-3.2.18+
diff -r linuxrpi-3.2.18/arch/arm/mach-bcm2708/bcm2708.c linuxrpi-3.2.18+/arch/arm/mach-bcm2708/bcm2708.c
34a35
> #include <linux/w1-gpio.h>
70a72,74
> // use GPIO 4 for the one-wire GPIO pin, if enabled
> #define W1_GPIO 4
> 
390a395,410
> 
> #if defined(CONFIG_W1_MASTER_GPIO) || defined(CONFIG_W1_MASTER_GPIO_MODULE)
> static struct w1_gpio_platform_data w1_gpio_pdata = {
> 	/* If you choose to use a pin other than PB16 it needs to be 3.3V */
> 	.pin		= W1_GPIO,
> 	.is_open_drain  = 0,
> };
> 
> static struct platform_device w1_device = {
> 	.name			= "w1-gpio",
> 	.id			= -1,
> 	.dev.platform_data	= &w1_gpio_pdata,
> };
> 
> #endif
> 
573a594,596
> #if defined(CONFIG_W1_MASTER_GPIO) || defined(CONFIG_W1_MASTER_GPIO_MODULE)
> 	platform_device_register(&w1_device);
> #endif
diff -r linuxrpi-3.2.18/drivers/i2c/busses/i2c-bcm2708.c linuxrpi-3.2.18+/drivers/i2c/busses/i2c-bcm2708.c
132,143d131
< static inline void bcm2708_bsc_fifo_drain(struct bcm2708_i2c *bi)
< {
< 	while ((bcm2708_rd(bi, BSC_S) & BSC_S_RXD) && (bi->pos < bi->msg->len))
< 		bi->msg->buf[bi->pos++] = bcm2708_rd(bi, BSC_FIFO);
< }
< 
< static inline void bcm2708_bsc_fifo_fill(struct bcm2708_i2c *bi)
< {
< 	while ((bcm2708_rd(bi, BSC_S) & BSC_S_TXD) && (bi->pos < bi->msg->len))
< 		bcm2708_wr(bi, BSC_FIFO, bi->msg->buf[bi->pos++]);
< }
< 
167c155
< 	bool handled = true;
---
> 	bool handled = false;
168a157
> 	struct i2c_msg *msg = bi->msg;
171a161
> 	handled = true;
183,184c173,177
< 		if (bi->msg->flags & I2C_M_RD)
< 			bcm2708_bsc_fifo_drain(bi);
---
> 		/* drain the RX FIFO */
> 		while (s & BSC_S_RXD) {
> 			msg->buf[bi->pos++] = bcm2708_rd(bi, BSC_FIFO);
> 			s = bcm2708_rd(bi, BSC_S);
> 		};
198c191,195
< 		bcm2708_bsc_fifo_fill(bi);
---
> 		/* fill the TX FIFO */
> 		do {
> 			bcm2708_wr(bi, BSC_FIFO, msg->buf[bi->pos++]);
> 			s = bcm2708_rd(bi, BSC_S);
> 		} while (s & BSC_S_TXD);
200c197,201
< 		bcm2708_bsc_fifo_drain(bi);
---
> 		/* drain the RX FIFO */
> 		do {
> 			msg->buf[bi->pos++] = bcm2708_rd(bi, BSC_FIFO);
> 			s = bcm2708_rd(bi, BSC_S);
> 		} while (s & BSC_S_RXD);
Solo in linuxrpi-3.2.18+: .git
My questions are:
1. do you have produced a more recentrly kernel with the 1wire support ?
2. If I enclose the lines form the diffi may the latest kernel works ?

Cheers and thanks for your great job !!

maui
Posts: 25
Joined: Sun Jul 08, 2012 10:10 am

Re: kernel patch for Dallas 1-wire interface

Fri Aug 10, 2012 8:01 pm

Hi,

I'm trying to get a DS18B20 working with the raspbian image.

Is the i2c patch includet? if not is there a update patch for the official raspbian image?
and is it possible to change the gpio pin?

without the patch I get

Code: Select all

pi@raspberrypi ~ $ sudo modprobe w1-gpio
ERROR: could not insert 'w1_gpio': No such device
so that means I need to patch, right? ;)

Darky
Posts: 8
Joined: Sun Aug 12, 2012 12:18 pm

Re: kernel patch for Dallas 1-wire interface

Sun Aug 12, 2012 12:20 pm

How can i Setup Linux .config variables: W1_MASTER_GPIO W1 W1_SLAVE_THERM?

And another secret, if i connect the GND and the 3,3 V withut any resitor the DS18S20 going very hot so the circuit from http://www.acmesystems.it/1wire doenst work for me :(

Andre-W
Posts: 24
Joined: Fri Jun 01, 2012 1:56 pm

Re: kernel patch for Dallas 1-wire interface

Sun Aug 12, 2012 2:38 pm

You need to compile the kernel by yourself with the patch or use an existing, already patched kernel. Simply setting some variables doesn't works.

If your DS18S20 is getting hot its "hot-wired" (short-circuited) - i'm sure you have interchanged the polarity (GND => 3V3 / 3V3 => GND). Please notice that the given polarity on the acme-site is from bottom view.

Darky
Posts: 8
Joined: Sun Aug 12, 2012 12:18 pm

Re: kernel patch for Dallas 1-wire interface

Sun Aug 12, 2012 2:58 pm

Tank yu now it works :)

I have only one problem left, i have installed this at firt http://www.raspberrypi.org/phpBB3/viewt ... =31&t=7471 for my wlan stick.

And now, after i installed the 1wire interface the wlan stick doesnt work anymore.

Andre-W
Posts: 24
Joined: Fri Jun 01, 2012 1:56 pm

Re: kernel patch for Dallas 1-wire interface

Sun Aug 12, 2012 3:03 pm

I think you need to re-install it because of the new kernel. But since i didn't now this installer/stick its just assumed. But i think it should work then.

MrEngman
Posts: 3601
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: kernel patch for Dallas 1-wire interface

Sun Aug 12, 2012 4:32 pm

Hi Frank,

Seems your kernel patch for the Dallas 1-wire breaks the rtl8188cus wifi driver. This is a module that is not included in the kernel source tree. To maintain a working version it needs updating as kernel versions change but to do this I need the kernel source.

Where can I find the source and patches you are using? Preferable from a source that I can use git clone/pull.

MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

User avatar
Frank Buss
Posts: 92
Joined: Fri Jan 06, 2012 4:39 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Tue Aug 14, 2012 2:35 pm

I've applied the patch to the Raspbian kernel, this is the new repository:

https://github.com/FrankBuss/linux/tree ... s-raspbian

To compile it yourself, you need to setup a toolchain with hard floating point support, as used for the Raspbian image (I tried it first without, but the kernel module loader crashed for some modules). See http://www.raspbian.org/RaspbianDocumentation and "Distcc Cross compiling for Raspbian" (you don't need to install distcc, but it describes how to use crosstoo-ng to create a cross compiler as well). Then check http://elinux.org/RPi_Kernel_Compilation if you want to know how to use this cross compiler to compile a new kernel.

The Raspbian image used the kernel from https://github.com/raspberrypi/linux, but looks like the defconfig was not the one which was used for the 2012-07-15-wheezy-raspbian.img image. So I've extracted the config from the original Raspbian image from "/proc/config.gz" and added my configurations to it and finally created a new defconfig with "make ARCH=arm savedefconfig" and updated "arch/arm/configs/bcmrpi_defconfig" with it.

If you don't want to compile your own kernel (the howtos are not very accurate from the Raspbian pastebin instruction, e.g. you need to convert the linefeeds from the downloaded config file, otherwise it won't compile), you can install my pre-compiled one. I've created a new script to update a Raspbian installation:

- first install the 2012-07-15-wheezy-raspbian.img (Raspbian “wheezy” from http://www.raspberrypi.org/downloads)
- customize your installation with Raspi-config, which is started at first boot, and finally execute the "update" menu item
- reboot (I've rebooted twice: first for expand_rootfs, then again, just in case :-)
- now you can update the kernel: login as root (or prefix the commands with "sudo") and download and execute the update script:

Code: Select all

rm -f raspbian-w1-update ; wget http://www.frank-buss.de/raspberrypi/raspbian-w1-update
bash raspbian-w1-update
This updates just the linux kernel image and the modules, because the firmware is already the current version.

Testing:

1-Wire:

Code: Select all

modprobe w1-gpio
modprobe w1-therm
cat /sys/bus/w1/devices/22-0000001d84f2/w1_slave
Should output something like this:

Code: Select all

b8 01 4b 46 7f ff 08 10 8a : crc=8a YES
b8 01 4b 46 7f ff 08 10 8a t=27500
(for 27.5°C)

I2C:

Code: Select all

modprobe i2c-bcm2708
modprobe i2c-dev
apt-get install i2c-tools
i2cdetect -y 0
With an attached PCA9555 at address 0x20 you should see something like this:

Code: Select all

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
SPI:

For SPI I've enabled the SPI dev, which was not enabled in the Raspbian image. With my kernel you can test it like this:

Code: Select all

modprobe spi-bcm2708
modprobe spidev
echo -n 42 > /dev/spidev0.0
This should show a signal like this on your scope (click on the image for full size) :
Image
As you can see, the default transfer rate is 500 kHz, but this can be changed with a kernel boot commandline parameter.

The Video 4 Linux, the new SPI and I2C driver and lots of other drivers, like the Prism2.5/3 USB driver or the RTL8192CU driver, were already enabled in the new image.

All differences between the original Raspbian image is the 1-wire patch and these configuration variables:

Code: Select all

CONFIG_W1=m
CONFIG_W1_MASTER_GPIO=m
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
CONFIG_W1_SLAVE_DS2408=m
CONFIG_W1_SLAVE_DS2423=m
CONFIG_W1_SLAVE_DS2431=m
CONFIG_W1_SLAVE_DS2433=m
CONFIG_W1_SLAVE_DS2760=m
CONFIG_W1_SLAVE_DS2780=m
CONFIG_W1_SLAVE_BQ27000=m
CONFIG_RTC_CLASS=y
CONFIG_RTC_DRV_DS1307=m
CONFIG_SPI_SPIDEV=m
I hope this will fix some other problems reported in this thread. If not, please post again or report new bugs and I'll try to fix it. Messages like "works like a charm" are welcome, too :-)

User avatar
Frank Buss
Posts: 92
Joined: Fri Jan 06, 2012 4:39 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Tue Aug 14, 2012 3:10 pm

Bah, can't edit posts. For the 1-wire test: "cat /sys/bus/w1/devices/22-0000001d84f2/w1_slave" depends on your connected 1-wire chip address and the address "22-0000001d84f2" is different for your chip (it is unique). Try "ls /sys/bus/w1/devices/" first.

davidmam
Posts: 101
Joined: Tue Dec 06, 2011 4:13 pm

Re: kernel patch for Dallas 1-wire interface

Tue Aug 14, 2012 3:46 pm

Many thanks for that. I was hoping you would provide a pre-compiled kernel as my cross-compiling options are limited.

Looking forward to trying it out tonight :) (and seeing if I have fried my UART GPIO pins, and if I can get the I2C ADC to work.)

rafal.deska
Posts: 3
Joined: Thu Jul 26, 2012 4:09 pm

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 1:14 am

Thanks for your job. Unfortunately the latest kernel doesn't work with 18B20 chip (previous version runs perfectly). There are no 1-wire devices in /sys/bus/w1/devices/w1 bus master directory:
driver uevent w1_master_max_slave_count w1_master_pullup w1_master_slave_count
power w1_master_add w1_master_name w1_master_remove w1_master_slaves
subsystem w1_master_attempts w1_master_pointer w1_master_search w1_master_timeout
lsmod shows loaded modules:
root@raspberrypi:/sys/bus/w1# lsmod
Module Size Used by
w1_therm 2977 0
w1_gpio 1563 0
wire 26105 2 w1_gpio,w1_therm
cn 5133 1 wire
I can't find any extended information in /var/log - dmesg shows only:
[ 105.658513] Driver for 1-wire Dallas network protocol.
Regards
Rafal

User avatar
Frank Buss
Posts: 92
Joined: Fri Jan 06, 2012 4:39 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 4:18 am

rafal.deska wrote:Thanks for your job. Unfortunately the latest kernel doesn't work with 18B20 chip (previous version runs perfectly). There are no 1-wire devices in /sys/bus/w1/devices/w1 bus master directory:
Yes, this is tricky. I don't know, if I did something wrong with the kernel configuration, or if the kernel changed this (which would be bad, because user mode program would break, if they don't do a switch-case based on the kernel version), but the path for the device with the previous version (kernel 3.2.18, based on bootc's kernel) was "/sys/bus/w1/devices/w1_bus_master1/22-0000001d84f2/w1_slave" and now (with kernel 3.1.9, based on the Raspbian kernel distribution) the path is "/sys/bus/w1/devices/22-0000001d84f2/w1_slave". And the 3.2.18 kernel uses "_" to separate the names in "w1 bus master", 3.1.9 uses spaces. Sorry, I didn't mentioned this change explicitly, just in the sample for the w1 test in my posting.

maui
Posts: 25
Joined: Sun Jul 08, 2012 10:10 am

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 8:33 am

Hi Frank,

I was waiting for the raspbian patch :)

After doing

Code: Select all

sudo bash raspbian-w1-update
my pi pachtes the kernel fine, then reboots and it stucks at the rainbow image ;)

But I saved my kernel before... so no big deal ;)
I tried 3 times ... :(

It isn't a "fresh" system. I installed XBMC, php, apache, gpio libs,..., may that be the cause?

What can I do now? do I need do cross compile :( ?

rafal.deska
Posts: 3
Joined: Thu Jul 26, 2012 4:09 pm

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 8:42 am

Thank you for reply. I resolved the problem - this was a hardware conflict with my bluetooth dongle. After unplugging it I can read back data at /sys/bus/w1/. Today I'll try to start to compile my own kernel.
Regards
Rafal

texy
Forum Moderator
Forum Moderator
Posts: 5015
Joined: Sat Mar 03, 2012 10:59 am
Location: Berkshire, England

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 11:29 am

Frank Buss wrote:
rafal.deska wrote:Thanks for your job. Unfortunately the latest kernel doesn't work with 18B20 chip (previous version runs perfectly). There are no 1-wire devices in /sys/bus/w1/devices/w1 bus master directory:
Yes, this is tricky. I don't know, if I did something wrong with the kernel configuration, or if the kernel changed this (which would be bad, because user mode program would break, if they don't do a switch-case based on the kernel version), but the path for the device with the previous version (kernel 3.2.18, based on bootc's kernel) was "/sys/bus/w1/devices/w1_bus_master1/22-0000001d84f2/w1_slave" and now (with kernel 3.1.9, based on the Raspbian kernel distribution) the path is "/sys/bus/w1/devices/22-0000001d84f2/w1_slave". And the 3.2.18 kernel uses "_" to separate the names in "w1 bus master", 3.1.9 uses spaces. Sorry, I didn't mentioned this change explicitly, just in the sample for the w1 test in my posting.
I don't quite follow this - is the 18B20 working with Raspbian......or not? ;)

Texy
Various male/female 40- and 26-way GPIO header for sale here ( IDEAL FOR YOUR PiZero ):
https://www.raspberrypi.org/forums/viewtopic.php?f=93&t=147682#p971555

Ste123
Posts: 19
Joined: Sat Aug 11, 2012 7:10 am

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 12:13 pm

I just followed the instructions from yesterday (14th Aug) and got it all working in a few minutes with a DS18B20

Thank-you Mr Buss.

asb
Forum Moderator
Forum Moderator
Posts: 853
Joined: Fri Sep 16, 2011 7:16 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 2:57 pm

Frank, would you like to submit a pull request against github.com/raspberrypi/linux?

User avatar
Frank Buss
Posts: 92
Joined: Fri Jan 06, 2012 4:39 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 3:00 pm

texy wrote:
Frank Buss wrote:
rafal.deska wrote:Thanks for your job. Unfortunately the latest kernel doesn't work with 18B20 chip (previous version runs perfectly). There are no 1-wire devices in /sys/bus/w1/devices/w1 bus master directory:
Yes, this is tricky. I don't know, if I did something wrong with the kernel configuration, or if the kernel changed this (which would be bad, because user mode program would break, if they don't do a switch-case based on the kernel version), but the path for the device with the previous version (kernel 3.2.18, based on bootc's kernel) was "/sys/bus/w1/devices/w1_bus_master1/22-0000001d84f2/w1_slave" and now (with kernel 3.1.9, based on the Raspbian kernel distribution) the path is "/sys/bus/w1/devices/22-0000001d84f2/w1_slave". And the 3.2.18 kernel uses "_" to separate the names in "w1 bus master", 3.1.9 uses spaces. Sorry, I didn't mentioned this change explicitly, just in the sample for the w1 test in my posting.
I don't quite follow this - is the 18B20 working with Raspbian......or not? ;)

Texy
With my DS1822 is works, and now others reported that it works with 1820, too. What I wanted to say was, that with the new kernel the path to the device changed :-)

User avatar
Frank Buss
Posts: 92
Joined: Fri Jan 06, 2012 4:39 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 3:17 pm

maui wrote:Hi Frank,

I was waiting for the raspbian patch :)

After doing

Code: Select all

sudo bash raspbian-w1-update
my pi pachtes the kernel fine, then reboots and it stucks at the rainbow image ;)

But I saved my kernel before... so no big deal ;)
I tried 3 times ... :(

It isn't a "fresh" system. I installed XBMC, php, apache, gpio libs,..., may that be the cause?

What can I do now? do I need do cross compile :( ?
Maybe you've installed other kernel modules, which are loaded at start? My update script was intended for a clean new installation, and it renames the /lib/modules/3.1.9+ directory , see the the update script content below. But when you say that just restoring the kernel rescued it, it can't be the modules.

Maybe no space left on /boot? This is a smaller partition than the others. You can try to execute the steps in the script at the commandline one by one (use ssh into the device, then you can copy-and-paste it). To verify that the download was ok, here are some checksums (you can verifiy it with "md5sum file", kernel.img=un-g'ziped and renamed kernel-raspbian-w1.gz) :

Code: Select all

57413f4aa5fedba721df41727ed22c26 kernel-raspbian-w1.gz
b0916f6d2a30c551f1935f5597255171 modules-raspbian-w1.tgz
c8c7bda5b0b4e2900f6ddd6c6024cec2 kernel.img
Sizes:

Code: Select all

2950309 kernel-raspbian-w1.gz
9094394 modules-raspbian-w1.tgz
6181884 kernel.img
Contents of /raspbian-w1-update:

Code: Select all

#!/bin/sh

# load: "rm -f raspbian-w1-update ; wget http://www.frank-buss.de/raspberrypi/raspbian-w1-update"
# start as root: "bash raspbian-w1-update"

cd /boot
rm -f kernel-raspbian-w1.gz kernel-raspbian-w1
wget http://www.frank-buss.de/raspberrypi/kernel-raspbian-w1.gz
gzip -d kernel-raspbian-w1.gz
mv kernel-raspbian-w1 kernel.img
cd /lib/modules
rm -f modules-raspbian-w1.tgz
rm -rf 3.1.9+.old
wget http://www.frank-buss.de/raspberrypi/modules-raspbian-w1.tgz
mv 3.1.9+ 3.1.9+.old
tar -xzvf modules-raspbian-w1.tgz
rm -f modules-raspbian-w1.tgz
sync
reboot

User avatar
Frank Buss
Posts: 92
Joined: Fri Jan 06, 2012 4:39 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 3:26 pm

asb wrote:Frank, would you like to submit a pull request against github.com/raspberrypi/linux?
sure, done.

maui
Posts: 25
Joined: Sun Jul 08, 2012 10:10 am

Re: kernel patch for Dallas 1-wire interface

Wed Aug 15, 2012 10:20 pm

Moin Frank,

I did the step by step install but got the same results -> stuck at rainbow screen.
So I wiped my long,good working image and did a fresh install of raspbian, and now ... it works :) :P

But is it normal after running "rpi-update" to patch the kernal again?

Thanks for your effort

User avatar
Frank Buss
Posts: 92
Joined: Fri Jan 06, 2012 4:39 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Thu Aug 16, 2012 4:43 am

maui wrote: I did the step by step install but got the same results -> stuck at rainbow screen.
So I wiped my long,good working image and did a fresh install of raspbian, and now ... it works :) :P
Good that it works now, but would have been interesting to know why it didn't worked for your installation. Maybe I should add a warning "can kill your running system, if it is not a clean Raspbian installation" in the update script :-) But it is a temporary solution anyway. I think my pull request for the official distribution looks good now, so that it will be integrated in the next official release.
maui wrote: But is it normal after running "rpi-update" to patch the kernal again?
I think the "update" menu item in "raspi-config" updates the "raspi-config" program itself, only. I don't know, if the update process for Raspbian can update the Linux kernel. I've tried "apt-get update" and there were no updated packages. But you are right, if the kernel are updated, you have to run the patch again.

maui
Posts: 25
Joined: Sun Jul 08, 2012 10:10 am

Re: kernel patch for Dallas 1-wire interface

Thu Aug 16, 2012 8:44 am

Good to know, that it will be in the next release :)

I know the raspi-config "update" only updates the sources ;)
you have to do a "apt-get upgrade" to install the new updates. But after the first install of the patch I did a rpi-update (firmware updater from Hexxeh) and I had to patch the kernal again after doing that.

EDIT: the rpi-update does update the kernel, but you can skip that with

Code: Select all

SKIP_KERNEL=1 rpi-update

davidmam
Posts: 101
Joined: Tue Dec 06, 2011 4:13 pm

Re: kernel patch for Dallas 1-wire interface

Thu Aug 16, 2012 10:30 am

I should say a big Thankyou to Frank for his hard work on this. I had it up and running with no problems. The only issue now is that when soldering my A2D converter I fried it somewhat so am now looking for a new one. Everything else works fine.

User avatar
Frank Buss
Posts: 92
Joined: Fri Jan 06, 2012 4:39 pm
Contact: Website

Re: kernel patch for Dallas 1-wire interface

Thu Aug 16, 2012 4:49 pm

maui wrote:But after the first install of the patch I did a rpi-update (firmware updater from Hexxeh) and I had to patch the kernal again after doing that.

EDIT: the rpi-update does update the kernel, but you can skip that with

Code: Select all

SKIP_KERNEL=1 rpi-update
Ok. I don't know which version of the firmware the rpi-update installs. The Raspbian distribution contains already a current one, e.g. you don't need to patch the kernel image anymore, like with older firmware from the first Debian distribution, so maybe no firmware update is needed. But maybe other bugs are fixed as well.

Return to “Interfacing (DSI, CSI, I2C, etc.)”

Who is online

Users browsing this forum: No registered users and 14 guests