#apertus IRC Channel Logs

Morning everyone

I know why I can not visit your web site.

at your company?

interesting

so your country considers my pages dangerous for the people :)

aha

something is dangerous

because it might just be that they block .at in general

http://www.nix.at/

ah, did you try to reach just www.13thfloor.at? or only the vserver.13thfloor.at address?

can not vist

both, interesting, well, if you need anything from there, you know how to get it :)

not yet.

I'm looking for a proxy software

OK

a software such as goagent

thanks.

yes?

please elaborate ...

The SD_Write() is interface for linux app. So we must not change it.

it can also be mounted by the kernel, so yes, we need different device nodes for the two micro SD cards

Oh,yes. I mean we no need changed the top level of the driver. if internal card's addr is 0xAXXXX and external is 0xBXXXXX , a simple I2C function added into SD_Write(). the I2C function controll which ADDR will be accessed.

the controller handling the card(s) has an address, but that is the same for both cards, as it is the same controller

is it xilinx PS can not give an address?

correct, the SD card is handled by the PS

the two cards use same controller

the SD bus is switched by the TXS02612

with the existing driver, yes

let's call them "first" and "second" card, because there is no internal and external

there is also the onboard SD interface on the microzed or zedboard

so, basically there are 3 variants how the two SD cards could be handled

2) by locking the interface to one card when it gets mounted/opened/etc

is it mean there are 3 cards in this system. One is onboard, the other two is our card_1st and card_2nd?

the onboard card is typically used to boot the microzed/zedboard

both connect to the second PS controller

Thanks

that won't work very well

linux can mount card_1st and card_2nd seperately?

then the driver receives commands to the first and the second device node and for each command/action, it has to check which card is actually accessed

if it is for the 'other' card, the driver first needs to switch the TXS02612 to the other interface

e.g. via round robin or first come first serve, etc

hmm?

ah, yes, the linux kernel has a driver which is capable of handling the SD controller used on zynq

(by switching to one card and then loading/activating the driver)

well, that's what I did manually to test the hardware with the existing driver

:)

correct

yeah.I know the condition now.

Can I know what's your major? Software?

Great!

okay, I'm off to bed now ... have a good one everyone!

Good night

hi