wooosaiii has quit [Remote host closed the connection]
wooosaii has joined #u-boot
wooosaii has quit [Remote host closed the connection]
wooosaii has joined #u-boot
aggi has quit [Quit: connection closed.]
prabhakarlad has joined #u-boot
aggi has joined #u-boot
minimal has joined #u-boot
wooosaii has quit [Remote host closed the connection]
wooosaii has joined #u-boot
m5zs7k has joined #u-boot
mintelodiaz has joined #u-boot
julienm has joined #u-boot
torez has joined #u-boot
mintelodiaz has quit [Read error: Connection reset by peer]
mintelodiaz has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
mintelodiaz has quit [Read error: Connection reset by peer]
mintelodiaz has joined #u-boot
wooosaii has quit [Read error: Connection reset by peer]
wooosaii has joined #u-boot
<julienm>
Hello all,
<julienm>
I would like to add the support of a new board (mediatek).
<julienm>
Several parts of the files/configs are taken from the kernel, however this board is not yet merged on the kernel (still under review).
<julienm>
Is-it common to wait the merge on the kernel and after that send to U-Boot ? (with links of the kernel patchs in commit msg ?)
<julienm>
Or can I send whatever the current state on kernel side ?
<julienm>
Thanks for your recommendations.
mintelodiaz has quit [Read error: Connection reset by peer]
mintelodiaz has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
pbergin has quit [Quit: Leaving]
mintelodiaz_ has joined #u-boot
mintelodiaz has quit [Ping timeout: 255 seconds]
mintelodiaz_ has quit [Read error: Connection reset by peer]
mmu_man has joined #u-boot
mintelodiaz_ has joined #u-boot
mthall has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
<apalos>
sjg1: I was looking at lib/smbios.c. The whole is revolving around the smbios node in the .dts
<apalos>
However the majority of the boards are lacking that and it's becoming annoying for distros which are used to rely on dmidecode etc
<apalos>
I'll prepare a patch where some reasonable defaults are applied from the base DT, e.g model and strip the manufacturer from the compatible node
mintelodiaz_ has quit [Read error: Connection reset by peer]
mthall has quit [Ping timeout: 255 seconds]
mthall has joined #u-boot
mintelodiaz_ has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
mintelodiaz_ has quit [Read error: Connection reset by peer]
mintelodiaz_ has joined #u-boot
mmu_man has joined #u-boot
mintelodiaz_ has quit [Read error: Connection reset by peer]
mintelodiaz_ has joined #u-boot
wooosaii has quit [Remote host closed the connection]
monstr has quit [Remote host closed the connection]
mintelodiaz_ has quit [Read error: Connection reset by peer]
mmu_man has quit [Ping timeout: 240 seconds]
mintelodiaz_ has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
<Forty-Bot>
julienm: for code it doesn't matter if the board is in Linux
<Forty-Bot>
for device trees the general rules is that it should be submitted to Linux as well, and won't be accepted in U-Boot until it is accepted in Linux
mintelodiaz_ has quit [Read error: Connection reset by peer]
mintelodiaz_ has joined #u-boot
guillaume_g has quit [Quit: Konversation terminated!]
mintelodiaz_ has quit [Read error: Connection reset by peer]
mintelodiaz_ has joined #u-boot
mintelodiaz_ has quit [Read error: Connection reset by peer]
minimal has quit [Remote host closed the connection]
minimal has joined #u-boot
mintelodiaz_ has joined #u-boot
<julienm>
Forty-Bot Thanks for the infos.
mintelodiaz_ has quit [Read error: Connection reset by peer]
mintelodiaz_ has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
thopiekar has quit [Quit: No Ping reply in 180 seconds.]
thopiekar has joined #u-boot
mmu_man has joined #u-boot
prabhakarlad has joined #u-boot
mintelodiaz_ has quit [Read error: Connection reset by peer]
mintelodiaz_ has joined #u-boot
frieder has quit [Remote host closed the connection]
mintelodiaz_ has quit [Read error: Connection reset by peer]
mintelodiaz_ has joined #u-boot
<sjg1>
hanetzer: Nice!
mintelodiaz has joined #u-boot
mintelodiaz_ has quit [Ping timeout: 252 seconds]
<sjg1>
apalos: I wish people would just embrace the device tree and use it. We don't have these problems with ACPI. There is also the sysinfo driver. We need to stop trying to turn U-Boot into EDK2 :-)
minimal has quit [Quit: Leaving]
wooosaii has quit [Remote host closed the connection]
wooosaii has joined #u-boot
<apalos>
sjg1: yea I implied sysinfo when I said smbios entry in the dts
<apalos>
However there's 2 options.
<apalos>
1. someone adds a .dtsi for *every* board
<apalos>
2. we make the sysnifo stuff have a reasonable fallback in the default dtb
<apalos>
there's several levels of failure in that lib/smbios thingy
<apalos>
e.g if sysinfo isn't compiled it doesn't even try to parse the smbios node in the .dtsi
<apalos>
I can have a look and fix most of these, but I dont really want to go over every board dts and add a .dtsi with an smbios node
<apalos>
but the defaults on DT are kinda sane. model == product in sysnfo speak and the manufacturer is the first element of the comma separated compatible root node
<apalos>
so i'd rather have code in there, that deals with missing sysninfo in a more reasonable way than "Unknown product"
julienm has quit [Quit: Client closed]
wooosaiii has joined #u-boot
wooosaii has quit [Read error: Connection reset by peer]
<Domon>
Hi, maybe someone can share some experience. If are some device, with NAND only, and already have inside bootloader + kernel + rootfs. How working with that setup (coding u-boot), and not broke bootloader (don't have NAND programmer)
mintelodiaz has quit [Read error: Connection reset by peer]
mintelodiaz has joined #u-boot
mintelodiaz has quit [Read error: Connection reset by peer]
mintelodiaz has joined #u-boot
wooosaiii has quit [Read error: Connection reset by peer]
wooosaiii has joined #u-boot
mintelodiaz_ has joined #u-boot
mintelodiaz has quit [Ping timeout: 252 seconds]
<sjg1>
apalos: How about adding a default sysinfo driver which does what you said? I would rather that than changing the core code to do special things
persmule has quit [Ping timeout: 258 seconds]
persmule has joined #u-boot
wooosaiii has quit [Remote host closed the connection]
wooosaiii has joined #u-boot
eloy has quit [Changing host]
eloy has joined #u-boot
wooosaiii has quit [Remote host closed the connection]
wooosaiii has joined #u-boot
wooosaiii has quit [Remote host closed the connection]
wooosaiii has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
<apalos>
sjg1: sure that sounds like an even better idea
<apalos>
I have a hacked version that works with model/compatible, I can just move that part of the code into a sysninfo driver and see what else might be missing
wooosaiii has quit [Read error: Connection reset by peer]
wooosaiiii has joined #u-boot
mmu_man has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
mintelodiaz_ has quit [Ping timeout: 260 seconds]
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
minimal has joined #u-boot
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
wooosaiiii has quit [Read error: Connection reset by peer]
wooosaiiii has joined #u-boot
prabhakarlad has joined #u-boot
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
matthias_bgg has quit [Quit: Leaving]
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii has joined #u-boot
wooosaiii has joined #u-boot
wooosaiiii has quit [Read error: Connection reset by peer]
persmule has quit [Ping timeout: 258 seconds]
persmule has joined #u-boot
GNUtoo has quit [Ping timeout: 258 seconds]
redbrain has quit [Ping timeout: 252 seconds]
redbrain has joined #u-boot
wooosaiii has quit [Remote host closed the connection]