Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
@MrNice: Should not matter.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
Okay, thx - now please continue with the tests popcornmix is asking for. I think what the firmware does, this "workaround" does fixed.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 8,966
Joined: Feb 2011
Reputation:
426
Copy start_x.elf and fixup_x.dat onto boot partition (e.g. what you see when plugging the card into Windows machine), renaming to overwrite the existing start.elf and fixup.dat.
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
Can you try to read a multiply of PACKET_SIZE?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
That really smells, that VFS is broken in a very nasty way.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,266
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,266
It does, if vfs has an issue with returning / fetching small values ... and it seems it had an effect.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.