ChanServ changed the topic of #linux-sunxi to: Allwinner/sunxi development - Did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait for an answer! - This channel is logged at https://oftc.irclog.whitequark.org/linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
<smaeul> MoeIcenowy: do you plan to send another version of your mkimage risc-v series soon? if not, is it okay if I do it?
ptf has joined #linux-sunxi
Mangy_Dog has quit [Ping timeout: 480 seconds]
<smaeul> on the subject of outstanding U-Boot patches, this one looks like it got forgotten: https://lore.kernel.org/u-boot/20210614002531.4b3f5ab9@slackpad.fritz.box/
ptf has quit [Ping timeout: 480 seconds]
cnxsoft has joined #linux-sunxi
pnill has joined #linux-sunxi
<MoeIcenowy> smaeul: you're okay
<MoeIcenowy> the unstable FEL on D1 makes me not so interested in hacking it now...
<smaeul> ah, I missed that
renze has quit []
renze has joined #linux-sunxi
macromorgan is now known as Guest2666
Guest2666 has quit [Read error: Connection reset by peer]
macromorgan has joined #linux-sunxi
macromorgan has quit [Read error: Connection reset by peer]
cmeerw has joined #linux-sunxi
Danct12 has quit [Ping timeout: 480 seconds]
cmeerw has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
Danct12 has joined #linux-sunxi
ptf has joined #linux-sunxi
mripard has quit [Ping timeout: 480 seconds]
lunixoid has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
tnovotny has joined #linux-sunxi
Daanct12 has joined #linux-sunxi
maz has quit [Quit: ZNC 1.8.1+deb1 - https://znc.in]
kmaincent has quit [Remote host closed the connection]
Danct12 has quit [Ping timeout: 480 seconds]
pnill has quit [Ping timeout: 480 seconds]
<ad__> "OrangePi PC2 board has DRAM with ODT" , it has internal DRAM ?
<ad__> or just programmable terminators for external sdram ?
lunixoid has quit []
<ad__> (just out of curiosity)
<ad__> yocto building (and rebuilding) gives time to study :)
pnill has joined #linux-sunxi
maz has joined #linux-sunxi
mripard has joined #linux-sunxi
warpme_ has joined #linux-sunxi
apritzel has joined #linux-sunxi
kmaincent has joined #linux-sunxi
Daanct12 has quit [Remote host closed the connection]
lunixoid has joined #linux-sunxi
lunixoid has quit []
buZz_ has joined #linux-sunxi
buZz has quit [Ping timeout: 480 seconds]
lunixoid has joined #linux-sunxi
buZz_ is now known as buZz
Danct12 has joined #linux-sunxi
Mangy_Dog has joined #linux-sunxi
lunixoid has quit []
lunixoid has joined #linux-sunxi
lunixoid has quit []
cnxsoft has quit [Remote host closed the connection]
lunixoid has joined #linux-sunxi
macromorgan has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
cmeerw has joined #linux-sunxi
<jernej> ad__: OrangePi PC2 has H5 SoC, which has no embedded DRAM
<jernej> ODT is supported in DRAM PHY
<jernej> that is standard feature
<jakllsch> the board has DRAM
<jakllsch> not the SoC. the statement you quoted didn't say that though..
<apritzel> smaeul: can you send an update for the TOC0 mkimage? I might be interested in taking both series then ...
vagrantc has joined #linux-sunxi
lunixoid has quit []
tnovotny has quit [Quit: Leaving]
<jernej> apritzel: there is only one board config, due to which I can't switch to FDTDIR in PXE config
<jernej> we have only single U-Boot config, for both, PineH64 model A and model B
<jernej> there are some minor differences between them
<jernej> actually, I'm not sure why LE supports model A, but I have it
<apritzel> jernej: I just have model A (only authentic with that patch wire), and nobody could apparently be bothered to send patches for model B yet, it seems
<jernej> I would rather make same trick as for pine64 (plus), if possible
<jernej> if not, I can send model B patches, but we are again at DT files issue
gsz has joined #linux-sunxi
<apritzel> yeah, not adding another defconfig is warmly welcomed
<apritzel> but yeah, the DT files ...
<jernej> but currently I have no clue if there is any defining difference to check in SPL
<apritzel> yeah, I was wondering this myself already, and I think I had a look in the schematics already, but didn't find anything quickly
<apritzel> maybe we can probe some GPIOs that are connected to the WiFi module, and check whether they are floating or stay at a fixed level?
<apritzel> I had some success with that to tell the Pine64-LTS apart from the Pinebook
<apritzel> (configure pull-up; read level; configure pull-down; read level; compare)
<jernej> IIRC there is wifi daughter board for model A
<apritzel> there is no need for you to spoil my fancy idea ;-)
<jakllsch> heh
<jernej> model A has a PCIe slot
<jakllsch> and some related gpios, iirc
<apritzel> right, and I think I tried that already, but they are just connected to the slot pins, so can't be distinguished from just floating because they are NC
<jernej> PCIE_REST_N (PG14) is pulled down
<apritzel> OK, will try that when I am home
<jernej> but I'm not sure if this is enough
<apritzel> does anyone have a model B to check on the other side?
<jakllsch> H64 model A here
<jakllsch> no B
<apritzel> (would just require typing some commands in U-Boot)
<jernej> yeah, I have both
<jernej> it's engineering sample, but except PH2, there should be no difference
<jernej> yeah, it should float
<jernej> so, what should I check?
<jernej> if it's floating, there is no guarantee which value I will get (at least not always)
<apritzel> jernej: but if you configure the pull-down/pull-ups, the level should follow
<apritzel> if it's fixed on the other end, it should not
<apritzel> but if it's pulled down externally, it might not work, depending on the resistor value
<jernej> exactly
<gamiee> PINE H64 model B owner here
<jernej> 10k pull down
<gamiee> What I need to check ?
<apritzel> if any board designer reads here: please spare three GPIOs to encode a board revision ;-)
<jernej> gamiee: set PG14 to input, set pull up and check you read 1, repeat with pull down
<jernej> apritzel: internal pull up/down resistance is 100k
<jernej> that should work imo
<jernej> 10k is much stronger
<apritzel> I dimly remember trying that already a while ago, but without success
<apritzel> I will check again later today
macromorgan has quit [Remote host closed the connection]
macromorgan has joined #linux-sunxi
<ad__> jernej, ok, thanks
<gamiee> jernej: will try in few secs
macromorgan has quit [Quit: Leaving]
macromorgan has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
<gamiee> jernej: `=> gpio input PG14` and result: `gpio: pin PG14 (gpio 206) value is 1`
<gamiee> (just I didn't found a way how to pull it up)
<jernej> via devmem :)
apritzel has joined #linux-sunxi
<gamiee> ah yeah, okay, let me check the registers
vagrantc has quit [Quit: leaving]
<jernej> apritzel: I just tested it on model A and it really behaves as there would be no external pull down
<jernej> alternatively, its resistance is much higher
apritzel has quit [Ping timeout: 480 seconds]
<gamiee> jernej: it seems to be 1 (hopefully I toggled the pins correctly) https://hastebin.com/kaxolakaqe.yaml
warpme_ has quit [Quit: Connection closed for inactivity]
<jernej> and if you change it to pull down? it's 0?
<jernej> apritzel: there is another difference - model A has SPI flash and model B has none
<jernej> gamiee: please disregard
<jernej> but thanks for testing
<jernej> apritzel: I looked at 1.0 schematic, there is pull down on PCIE_REST_N
<jernej> apritzel: however, on 1.1 is marked as NC
<jernej> SPI flash is our best bet, it would seem
<jernej> meh, SPI flash is also present on model B
<jernej> I just missed it
<gamiee> jernej: switched to pull-down and the bit is 0, so seems like it works
<jernej> yeah, we are looking for some pin, which would have different behaviour between model A and B
<jernej> we hoped that PG14 has pull down, which would clamp value
<gamiee> same behavior is also on Model A?
<jernej> but they removed that pull down in final revision
<jernej> so yes, same behaviour
<jernej> in short, there is no difference that we could exploit to determine which model it is
<gamiee> hmm thinking what can be different
<jernej> only differences in DR files are ddc-en for hdmi and gmac power regulator
<jernej> *DT
apritzel has joined #linux-sunxi
<jernej> ddc-en is not really useful - it has no pull up or pull down and it's also connected to GPIO header, so it can be used for something else
<apritzel> jernej: is the PHY a different model?
<apritzel> nothing easily exploitable from SPL, though
<gamiee> Also, it's most possible that SPI Flashes are different, but that's hard to probe and can be changed anytime
<jernej> PHYs are same and SPI flashes look same size
<jernej> I think they are from different manufacturers, but that doesn't mean much
<gamiee> BTW, isn't there only small amount of Model A around ? Is it worth ?
<apritzel> let's fix broken U-Boot proper SPI support for the H6 first ;-)
<jernej> gamiee: current U-Boot config is for model A
<jernej> so either we find something for autodetection or we add another for model B
<gamiee> apritzel: it's broken? I remember I made patch for SPL SPI support and sent it, but it didn't get merged
cmeerw[m] has joined #linux-sunxi
<apritzel> gamiee: pretty sure SPL SPI support works (did you check that recently?), but proper SPI support is completely separate
cmeerw has left #linux-sunxi [Leaving]
<jernej> apritzel: why do you need SPI support?
<apritzel> to check the manufacturer (and to eventually store the environment and UEFI variables, though that's another story)
JohnDoe_71Rus has quit []
<apritzel> so my (really early) model A says: Winbond w25q64dw, 8 MB
<apritzel> (id: 0xef6017, ext_id: 0)
<apritzel> isn't that supposed to be 16MB/128Mbit?
<jernej> it is, yes
gsz has quit [Quit: leaving]
megi1 has quit []
megi has joined #linux-sunxi