<snkt>
can some one help me how change kernel command line parameter without reflashing a whole linux linaro image?
hipboi has joined #radxa
naobsd has joined #radxa
hipboi has quit [Ping timeout: 246 seconds]
hipboi has joined #radxa
akaizen has quit [Remote host closed the connection]
akaizen has joined #radxa
akaizen has quit [Ping timeout: 272 seconds]
akaizen has joined #radxa
hipboi has quit [Ping timeout: 245 seconds]
hipboi has joined #radxa
naobsd has quit [Ping timeout: 246 seconds]
bengal has joined #radxa
bengal_ has joined #radxa
bengal has quit [Remote host closed the connection]
bengal_ has quit [Remote host closed the connection]
bengal has joined #radxa
mrcan_ has joined #radxa
mrcan has quit [Ping timeout: 258 seconds]
bengal has quit [Ping timeout: 245 seconds]
naobsd has joined #radxa
<c0d3z3r0>
snkt: upgrade_tool di -p [parameter file]
<snkt>
c0d3z3r0, thanks... I got that..
<snkt>
c0d3z3r0, can I know exact kernel config of linaro ubuntu 13.09
<c0d3z3r0>
when you boot it up you could just do cat /proc/config.gz
<snkt>
ok.. let me check...
<snkt>
c0d3z3r0, after every reboot ethernet MAC ID get change... Radxa don't have unique Ethernet card?
<c0d3z3r0>
I have the same problem and I don't know if it is a bug or if there is no unique mac. you can set mac adress adding mac_addr=00:00:00:00:00:00 to the cmdline in your parameter file
<snkt>
c0d3z3r0, its work with mac_addr= parameter... but for different radxa unit always need to set diff mac_addr parameters...
<c0d3z3r0>
right
<snkt>
c0d3z3r0, I am working different rockchip rk3188 production board... some dongles, some are like thinclients
<naobsd>
no unique mac. most RK products use wifi mac address for ether too
<naobsd>
^no unique mac for ether
<c0d3z3r0>
same mac adress for wifi and ethernet? :O
<naobsd>
technically no problem unless try to connect both interfaces to same network
<naobsd>
and Android doesn't connect 2 network same time
<snkt>
naobsd, same with Android?
<snkt>
i working on linux based OS for rockchip rk3188 for digital signage application
<naobsd>
naobsd: I talked about Android, and not all RK3188 Android does it. some or many does it.
<naobsd>
oops
<naobsd>
snkt: ^
<naobsd>
snkt: you can do same(use same mac address from wifi) on Linux unless you want to connect both ether/wifi to same network segment
<naobsd>
connect same network at same time
<snkt>
naobsd, OK apart from Ethernet...... Do we get any other Unique ID to differentiate units... I want something to bind with licence
<naobsd>
snkt: I think Radxa (Rock) doesn't have such a unique id
<snkt>
naobsd, CONFIG_ETH_MAC_FROM_IDB=y ... how its work... can you please help me ... do you have any idea?
<naobsd>
snkt: but probably you can set some kind of unique id to each units
<naobsd>
snkt: I never tried but probably some tool named Factory Tool or something like that can set that information
<snkt>
naobsd, but that unique ID might come at user space ?
<naobsd>
to IDB (=somewhere on NAND)
<naobsd>
snkt: no idea for now. but if CONFIG_ETH_MAC_FROM_IDB works as expected with that tool, you can get mac address of eth0 on userland
<naobsd>
^you can get unique mac address (you set by tool) on userland
<snkt>
naobsd, Ok... vll check...... Actually I have another unit provided by some vendor cloudsto with ubuntu 12.04... and found in dmesg as " eth_mac_from_idb*********:<mac id>"
<snkt>
naobsd, unfortunately I have only one unit to compare Uniqueness of MAC
<naobsd>
about setting uid into IDB(NAND)
<naobsd>
if your user erases NAND completely, uid will be erased too
<naobsd>
(normal update should be ok)
<naobsd>
there is eFUSE in RK3188
<naobsd>
but I have no idea how to use it for now
<snkt>
ok... vll do some study on it...
<c0d3z3r0>
"eFuse, only accessed by Cortex-A9 in security mode
<naobsd>
current kernel reads eFUSE to identify 3188 or 3188T
<naobsd>
no problem to read from kernel
<c0d3z3r0>
I'll take a look on the source
<snkt>
how can we access from userspace ?
<naobsd>
I said no idea
<naobsd>
btw, it's not factory tool, it's UpgradeDllTool in RKTools in SDK
<naobsd>
for setting MAC
<naobsd>
but I don't know how to use it and it really works
<snkt>
naobsd, ok ... i will give a try...
<naobsd>
alternative way
<naobsd>
you can add a partition
<naobsd>
to store anything for your product
<naobsd>
it can be accessed from /dev/... as standard MTD device
<naobsd>
you have to flash unique partition image for every units, but it's almost same task for setting unique MAC for every units
<naobsd>
that tool is for Windows
<naobsd>
but for "your own partition" way, you can use rkflashtool on Linux
<naobsd>
if you want to protect unique information from user, "your own partition" is relatively weak, but user can change MAC with that tool
<c0d3z3r0>
i think snkt want's to calculate a licence key for his product which only works on one unique device. am I right?
<naobsd>
if you need to protect unique info, probably it will be better to sign unique info with RSA or something like that, then flash signed info into partition
<naobsd>
I will not use MAC as key
<naobsd>
^personally
<c0d3z3r0>
that's why he asked if there is any unique id :) maybe I'm wrong...
<naobsd>
but putting signed unique info into partition (without unique hardware id on board) also doesn't help e.g. if user have 2 units, he can copy signed info
<naobsd>
^if user have 2 units, 1 restricted license and 1 full license,