Issue #3044 has been updated by sepherosa.
It will be great, if this can be automated. On Tue, Jun 20, 2017 at 4:39 AM, <bugtracker-ad...@leaf.dragonflybsd.org> wrote: > Issue #3044 has been updated by sucan...@fit.cvut.cz. > > > swildner wrote: >> Thanks, I've checked the patches and they work on this 1020 card I own >> (using isp_1040 firmware I suppose). >> >> How exactly did you generate the *.uu files? How would we sync it with >> FreeBSD's in the future? > > I generated the *.uu files using command-line tools. I > > - removed all lines from a C header file keeping only those lines with values > of an array for one firmware image (e.g. 0x1234, 0x5678, ...) > - transformed the values (swapped the bytes to be in little-endian order) > using sed to an arguments for the bash-builtin printf command (printf > "\x34\x12"; printf "\x78\x56"; ...) > - executed generated printf calls as a bash script and redirected stdout to a > file > - converted the binary file with uuencode > - concatenated the .uu file with a corresponding license text > > About the sync with FreeBSD's: the truth is I didn't think about that. > > ---------------------------------------- > Submit #3044: isp: Unify firmware handling with the rest of the system. > http://bugs.dragonflybsd.org/issues/3044#change-13167 > > * Author: sucan...@fit.cvut.cz > * Status: In Progress > * Priority: Normal > * Assignee: swildner > * Category: > * Target version: > ---------------------------------------- > Hello, > > these patches convert firmware binary data from C arrays in a header files to > uuencode .uu files. Byte order of the firmware image is little-endian. As far > as DragonFly BSD supports only little-endian architectures it's ok. But in > case of a big-endian architecture the byte order must be changed before > firmware is processed by the isp driver. They also move the .uu images to a > sys/contrib/dev/isp. > > The first part concerns these firmwares: isp_1040, isp_1040_it, isp_1080, > isp_1080_it, isp_12160, isp_12160_it, isp_2100, isp_2200, isp_2300 and > isp_2322. > The second part concerns these firmwares: isp_2400, isp_2400_multi, isp_2500, > isp_2500_multi. > > The division is needed because a size of a single patch must be less than 5 > MB for the bugtracker to accept. > > > ---Files-------------------------------- > 0001-isp-Unify-firmware-handling-with-the-rest-of-the-sys.patch (3.47 MB) > 0002-isp-Unify-firmware-handling-with-the-rest-of-the-sys.patch (4.02 MB) > > > -- > You have received this notification because you have either subscribed to it, > or are involved in it. > To change your notification preferences, please click here: > http://bugs.dragonflybsd.org/my/account -- Tomorrow Will Never Die ---------------------------------------- Submit #3044: isp: Unify firmware handling with the rest of the system. http://bugs.dragonflybsd.org/issues/3044#change-13168 * Author: sucan...@fit.cvut.cz * Status: In Progress * Priority: Normal * Assignee: swildner * Category: * Target version: ---------------------------------------- Hello, these patches convert firmware binary data from C arrays in a header files to uuencode .uu files. Byte order of the firmware image is little-endian. As far as DragonFly BSD supports only little-endian architectures it's ok. But in case of a big-endian architecture the byte order must be changed before firmware is processed by the isp driver. They also move the .uu images to a sys/contrib/dev/isp. The first part concerns these firmwares: isp_1040, isp_1040_it, isp_1080, isp_1080_it, isp_12160, isp_12160_it, isp_2100, isp_2200, isp_2300 and isp_2322. The second part concerns these firmwares: isp_2400, isp_2400_multi, isp_2500, isp_2500_multi. The division is needed because a size of a single patch must be less than 5 MB for the bugtracker to accept. ---Files-------------------------------- 0001-isp-Unify-firmware-handling-with-the-rest-of-the-sys.patch (3.47 MB) 0002-isp-Unify-firmware-handling-with-the-rest-of-the-sys.patch (4.02 MB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
