Tree: 49e9ea898f

main

20190312

20190416

20190514

20190618

20190717

20190815

20190923

20191022

20191215

20200122

20200316

20200421

20200519

20200619

20200721

20200817

20200918

20201022

20201118

20201218

20210208

20210315

20210511

20210716

20210818

20210919

20211027

20211216

20220209

20220310

20220411

20220509

20220610

20220708

20220815

20220913

20221012

20221109

20221214

20230117

20230210

20230310

20230404

20230515

20230625

20230804

20230919

20231030

20231111

20231211

20240115

20240220

20240312

20240410

20240513

20240610

20240709

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '49e9ea898f'

${ noResults }

Commit Graph

1 Commits (49e9ea898f870ae09b91ccd3dd1c45d520fcb0c3)

Author	SHA1	Message	Date
Jaswinder Singh	5c5a083a9f	vicam: use request_firmware() ... Although it wasn't actually using ihex records before, we use the Intel HEX record format for this firmware -- because that gives us a simple way to split it into separate chunks internally as we need, without loading each part as a separate file. Signed-off-by: Jaswinder Singh <jaswinder@infradead.org> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>	17 years ago