<sjoerd>
(that's also using upstream u-boot with some of my patches on top)
<rperier>
nice :)
nighty-_ has joined #linux-rockchip
markm has quit [Ping timeout: 255 seconds]
markm has joined #linux-rockchip
ssvb has quit [Ping timeout: 250 seconds]
ssvb has joined #linux-rockchip
markm_ has joined #linux-rockchip
markm has quit [Ping timeout: 264 seconds]
ssvb has quit [Ping timeout: 252 seconds]
ssvb has joined #linux-rockchip
naobsd has quit [Remote host closed the connection]
<sjoerd>
mmind00: fwiw my issue with the uart not correctly going to high rates is due to the uart driver never actually changing the input clocks :)
<sjoerd>
mmind00: All the driver does, from what i can tell, configure the dividers in the uart ip itself with min/max depending on the input clock setting
maz has joined #linux-rockchip
<lautriv_>
need some ideas. i have a box booting androshit with 2G RAM, tested some sd-bootable linux where it shows only 1G. already replaced paramaters and kernel but still 1G. the initramfs from boot.img is empty (all zeros) what may affect it ?
<lautriv_>
... and loaders are the same
markm_ has quit [Ping timeout: 268 seconds]
markm_ has joined #linux-rockchip
maz has quit [Ping timeout: 240 seconds]
sunilmohan_w has quit [Ping timeout: 246 seconds]
sunilmohan_w has joined #linux-rockchip
lautriv_ has quit [Ping timeout: 244 seconds]
ssvb has quit [Ping timeout: 264 seconds]
lautriv_ has joined #linux-rockchip
markm_ has quit [Ping timeout: 246 seconds]
markm_ has joined #linux-rockchip
<em|biketron>
lautriv_: so you're may using and DeviceTree with only 1G listed in it?
ssvb has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 255 seconds]
maz has joined #linux-rockchip
dlezcano has quit [Ping timeout: 250 seconds]
cnxsoft has quit [Quit: cnxsoft]
dlezcano has joined #linux-rockchip
<mmind00>
sjoerd: so your max speed is the one of the input clock
<sjoerd>
mmind00: ack
<sjoerd>
The default setting of the input clock even
<sjoerd>
which is lower then the 4mbit/s the bluetooth driver wants to set it to :)
<sjoerd>
thus confusion allround
<rperier>
does someone here use the drive "nxp,pca954x" this is for i2c muxing... just in case ?
<rperier>
a lot of dts use the property "nxp,pca9548" (the zc702 for example) , the problem is that the driver does not expose of_device_id identifiers... so the kernel is not able to bind the driver to the corresponding device
<sjoerd>
rperier: that goes via the old i2c table method right ?
<rperier>
mhhhhh
<rperier>
really?
<sjoerd>
Yeah the i2c core checks both iirc
<rperier>
yeah the driver only seems to export the old i2c table... I think that I should propose a patch which enable dts support between #ifdef CONFIG_OF" .... because I think that this is an important feature nowadays