Age | Commit message (Collapse) | Author | Files | Lines |
|
Let the linker find libmtp / libusb. Also don't insist on linking them
statically -- current Debian doesn't have a static libmtp.
Set STATIC to force linking statically.
Change-Id: I3ce9cea832705c87f08054435eadf9f169afedb2
|
|
The multiprocessing module is part of Python since 2.6, so no need to do
an extra check here.
Change-Id: If1c223edf9f04b6de8fdf757ba00f79897783a53
|
|
Change-Id: I8acbe43e3f27e51159a7a78fcc361476d7406cbb
|
|
ypr1 target should switch back to OF by pressing volume down,
since volume up is already mapped to the early/safe mode.
Change-Id: I18c4deed2c8982dbee18b081ecc59b970c654473
|
|
This trivial patch wants to exploit /tmp filesystem to place
Rockbox executable. Why that? It will be then possible to
easily unlock & umount the storage partition, in order to provide
Rockbox itself a mean for RAW storage access. In turn, this will
allow a Rockbox-handled USB Mass Storage support, as well as other
goodies (storage info is one I can think of).
It takes way less than a second so it doesn't hurt boot time.
Moreover, YPR0/YPR1 targets have plenty (64MB) of RAM, so
the humble half meg executable won't hurt at all.
Change-Id: Ibc9d9a40712e924c8e19cfd7c62189b182f0401a
|
|
This patch removes the deprecated kernel module to manage
the fm-radio chip on the ypr0 target.
http://gerrit.rockbox.org/r/#/c/1594/ implements the interface to
the i2c bus by using the i2c-dev kernel driver, no need for
additional complexity.
Change-Id: I0d09e2e9d1714b3cb8a72b3d79a91602a627cc90
|
|
Only expand pkg-config calls once by making the compiler flags simply
expanded variables. Makes things more predicable and slightly faster.
Change-Id: Ie2ed066f205a95ec8a7708cefeb29e9989815db6
|
|
Change-Id: Iff92a1f6a918f7da80f26f1a9ca02a6f6f082b7d
|
|
Fix various pylint issues and some python3 compatibility.
Change-Id: I2c35ccc5ad2d0902c229f9de57912cf6d5a83ece
|
|
Building with mxe failed due to the toolchain (and Qt5) introducing
dependencies to system libraries we don't know about. Commit 3083abeb95
thus ignored the actual problem. Revert that and instead add the missing
system libraries to the list of known libraries.
Change-Id: I29ac296765e580b751d3d906d58ab563d05efde2
|
|
(This migration happened over a decade ago!)
Change-Id: Ib396414a16f2d763e549af49e3f3b03047dab49c
|
|
Change-Id: I4a7a9688af1abb14de82013703f3a02b4644d5ed
|
|
Change-Id: I692b06c7c456bfa4395aa2aa848fdc664bd203d4
|
|
This can be useful to quickly device usb traces
Change-Id: I843fbd5280f11686ea810b44ffb1414e844ebcf9
|
|
Change-Id: Ia20f0142a2b08bddd61a0056f49c8e4c9ed49caa
|
|
At least newer devices support more NVP properties in a device-independent
numbering. Many are supported but I just added two useful ones
Change-Id: I57926de7f0dd364b46a57ca8d48a5c4d4f20402b
|
|
Newer devices seem to require flags 0x00 where older devices wanted 0x80, now
try both variants
Change-Id: Ifeee641052857c66c1b64860d7309a235021a168
|
|
Change-Id: I43c5101502f3d2c34296b510b738276fd74f9b3d
|
|
Change-Id: I350553db037ad9f65aced3f974afeaeee3fe822a
|
|
Change-Id: I963028c6017796152a201791c078f672bf84a40a
|
|
Change-Id: I8997e7c3791b805a70a30cd1209a69b7afbec1e7
|
|
Change-Id: I8977e1bcc805df463f7b08f11be889368db4eab2
|
|
Change-Id: I8f393a53ea64c82f05e437923bcba05aa8a7a75c
|
|
Change-Id: Ib2c25dd21d39fda026e008950a805f032c916a72
|
|
Change-Id: Ic14bc5ff643c9cf4c6380b4c34999d704c65e460
|
|
Change-Id: I07e57218638ef62c0e4bf92833add6c3ba7bdcd8
|
|
This helps with MXE static builds, which were failing because no DLLs were
found.
Change-Id: Id3fcdf9a7682a9ecb6a5892415077bf16e8b24cb
|
|
Change-Id: Ic6d998441fb532a914eea2838fdc0d196f930bb2
|
|
This fixes a couple of issues when cross-compiling for windows:
- lib builds (i.e. mks5lboot) were overriding the cross CC/CXX with the
native CC, producing incompatible binaries.
- Qt made the accessibility plugin part of the core library, so we no
longer need to import it.
Change-Id: I9d884aee62dfa51d3624a3fa9b99c23b3b375f20
|
|
Seems like newer versions of mingw will sponteanously add a .exe suffix to
the output path if it doesn't have one, for example mingw-gcc -o scsitool bla
will actually create scsitool.exe and of course this breaks my release script.
Fix this by explicitely adding the .exe to avoid any problem
Change-Id: Ic8019b968b532b2ca612ba0c03977a96c22cee01
|
|
This is one of those fancy gold-plated devices. Of course it breaks my scripts
that were nicely expecting every device to start with NW.
Change-Id: I161320f620f65f4f92c2650d192b26a9831eeb9d
|
|
Necessary to get working builds on my Fedora 29 system.
Change-Id: Ia6232427c959629ade9a85fc412738f688facedb
|
|
There is something weird going on: the Sony website has two different entries:
- NW-ZX300/NW-ZX300A/NW-A45/NW-A47/NW-A45HN/NW-A46HN
- NW-ZX300,NW-ZX300A update(20181004)/NW-ZX300G
with slightly different nvp entries, but it is impossible to tell whether
an NW-ZX300(A) belong to one or the other. Since the diff is very small,
I am adding this as nw-zx300g but treat all devices as nz-zx300 since the
destination node is the same and that is the main usage of the tool anyway.
Change-Id: I3dc2fdec52650f938d568bed578184f6bc43d130
|
|
Change-Id: I9bbfa56c5b2d79568de5443f1098d724c4beda6a
|
|
If the model is not known (ie model ID in the database) but another device from
the same series is known, then the database information probably applies and
one can use the "force" option -s to tell the tool to ignore the model ID.
Automatically print such advice when the series can be guessed.
Change-Id: I6bcc7aa29693df8c3d7d8e709ece7cea650be717
|
|
Change-Id: Ic4f382667c5c84514be661d36032c47fb8f92e75
|
|
For now it is only implemented on linux using /sys scanning
Change-Id: Ifdfe7564e6e8d0307ae6ddc53e49bb9aaf5a8268
|
|
Change-Id: Ia0f96dd27c520cf2bfec4765619f53eaffee3e20
|
|
For some reason even Sony didn't have it in its list...
Change-Id: I26de6071e5887cc7c6ebb695ea333c7b3d1b50db
|
|
Change-Id: I49f3399552721e515cc01021c2e0aa28c781ec28
|
|
Change-Id: I59861119c59490f586b3c6ed32a1c41df8b3d365
|
|
swr/swl instructions used for word aligning were wrong. This
made memset() terribly broken. I can't imagine how it went
uncaught for soooo long. Spotted by Solomon Peachy.
I run unit tests for alignments 0,1,2,3
size 1, 2, 3, 4, 5, 63, 64, 65, 127, 128, 129;
and fill pattern 0x00 and other (since 0 is special case in this
implementation).
Change-Id: I513a10734335fe97734c10ab5a6c3e3fb3f4687a
|
|
Change-Id: I3771388d24fe5fa249dcb40b231d7a4e06d3c3c8
|
|
Change-Id: I13b20b88b35e825da929a31e71ff42d68a79f131
|
|
Change-Id: I4c48c9a8d862eaf67ec27c1c13b9b7f1fb204fc0
|
|
Change-Id: I37671ddf15ee1a4b469f97fe06ec86249ff9ce60
|
|
Change-Id: I083024662f3c085f7bcd2f85b0a68de85725b0f3
|
|
Previously only atomic read/write 8/16/32 were exposed. But it is useful to
be able to read a whole buffer at once, this is more efficient than N times
read8.
Change-Id: I06e331641e1ab1f74c0e16e8c432eafb398e8e6d
|
|
It's a wonder it worked, basically any big transfer returned garbage
Change-Id: Ic2b2fc1805423c70db8eac40692ba842c72462ab
|
|
Change-Id: Ic46c724c5d89a775dc20853410c8fe6f0ff9a4c8
|