Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1130571 > unrolled thread

Bug#1016963: Help with testing u-boot!

Started byVagrant Cascadian <vagrant@debian.org>
First post2022-12-29 00:30 +0100
Last post2023-01-05 17:40 +0100
Articles 20 on this page of 35 — 7 participants

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1016963: Help with testing u-boot! Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 00:30 +0100
    Bug#1016963: Please test u-boot for rpi_3 rpi_3_32b Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:10 +0100
    Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:20 +0100
    Bug#1016963: Please test u-boot for rpi_4 bananapi_m2_berry rpi_4_32b Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:20 +0100
    Bug#1016963: Please test u-boot for orangepi_one_plus Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:30 +0100
    Bug#1016963: Please test u-boot for colibri_imx6 Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:40 +0100
    Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:40 +0100
      Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck Ian Campbell <ijc@debian.org> - 2022-12-29 13:30 +0100
        Bug#1016963: Please test u-boot for dreamplug Vagrant Cascadian <vagrant@debian.org> - 2023-01-21 21:20 +0100
          Bug#1016963: Please test u-boot for dreamplug Ian Campbell <ijc@debian.org> - 2023-01-22 10:00 +0100
      Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck Ian Campbell <ijc@debian.org> - 2022-12-29 18:10 +0100
    Bug#1016963: Please test u-boot for dh_imx6 Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:40 +0100
    Bug#1016963: Please test u-boot for sheevaplug mx6cuboxi Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:40 +0100
    Bug#1016963: Please test u-boot for am335x_boneblack am335x_evm Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:50 +0100
    Bug#1016963: Please test u-boot for nitrogen6q sifive_unleashed Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:50 +0100
    Bug#1016963: Please test u-boot for mx53loco wandboard igep00x0 omap3_beagle omap4_panda Cubietruck Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:50 +0100
    Bug#1016963: Please test u-boot for Linksprite_pcDuino Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for A20-OLinuXino_MICRO-eMMC Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for Mini-X Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
      Bug#1016963: Please test u-boot for Mini-X Jochen Sprickerhof <jspricke@debian.org> - 2023-01-04 23:40 +0100
        Bug#1016963: Please test u-boot for Mini-X Jochen Sprickerhof <jspricke@debian.org> - 2023-01-06 18:10 +0100
    Bug#1016963: Please test u-boot for A20-OLinuXino-Lime2-eMMC Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for Linksprite_pcDuino3 Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for Bananapi_M2_Ultra Sinovoip_BPI_M3 Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for orangepi_zero Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:10 +0100
    Bug#1016963: Please test u-boot for nanopi_neo_air Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:10 +0100
    Bug#1016963: Help with testing u-boot! "Rick Thomas" <rick.thomas@pobox.com> - 2022-12-29 04:00 +0100
    Bug#1016963: Help with testing u-boot! "Rick Thomas" <rick.thomas@pobox.com> - 2022-12-29 04:30 +0100
      Bug#1016963: Help with testing u-boot! Vagrant Cascadian <vagrant@debian.org> - 2023-01-06 01:10 +0100
    Bug#1016963: Help with testing u-boot! "Rick Thomas" <rick.thomas@pobox.com> - 2022-12-29 04:40 +0100
    Bug#1016963: Help with testing u-boot! Reco <bugs@enotuniq.net> - 2022-12-29 07:40 +0100
    Bug#1016963: Help with testing u-boot! Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 11:20 +0100
    Bug#1016963: Please test u-boot for rock-pi-4-rk3399 Walter Lozano <walter.lozano@collabora.com> - 2023-01-03 13:20 +0100
    Bug#1016963: Please test u-boot for rock-pi-4-rk3399 Christopher Obbard <chris.obbard@collabora.com> - 2023-01-05 16:20 +0100
      Bug#1016963: Please test u-boot for rock-pi-4-rk3399 Christopher Obbard <chris.obbard@collabora.com> - 2023-01-05 17:40 +0100

Page 1 of 2  [1] 2  Next page →


#1130571 — Bug#1016963: Help with testing u-boot!

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 00:30 +0100
SubjectBug#1016963: Help with testing u-boot!
Message-ID<FHO1X-dYj2-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-22, Vagrant Cascadian wrote:
> On 2022-08-20, Vagrant Cascadian wrote:
>> On 2022-08-10, Vagrant Cascadian wrote:
>>> This bug is just to delay migration to testing while more platforms get
>>> tested. If you have a relevent board, please consider testing and
>>> reporting the status:
>>>
>>>   https://wiki.debian.org/U-boot/Status

I have not received many test results for current or even remotely
recent u-boot platforms in Debian, and u-boot has been blocked from
migration to testing partly because of this.

As the bookworm freeze approaches, this is getting to be... worrysome!

If you have access to any of these boards, please consider testing
u-boot versions as packaged in debian for versions from debian stable
(2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
(2023.01-rc*) and updating the wiki page if successful and/or replying
to 1016963@bugs.debian.org with a positive confirmation...

...and if not successful, filing bugs against the relevent u-boot-*
packages and marking them as blocking 1016963.

# arm64
khadas-vim
khadas-vim2
libretech-cc
nanopi-k2
odroid-c2
odroid-n2
mvebu_espressobin-88f3720
dragonboard410c
dragonboard820c
firefly-rk3399
nanopc-t4-rk3399
nanopi-neo4-rk3399
pinebook-pro-rk3399
puma-rk3399
roc-pc-rk3399
rock-pi-4-rk3399
rock-pi-e-rk3328
rock64-rk3328
rockpro64-rk3399
rpi_3
rpi_4
rpi_arm64
a64-olinuxino
a64-olinuxino-emmc
nanopi_neo2
nanopi_neo_plus2
orangepi_one_plus
orangepi_zero_plus2
pine64-lts
pine64_plus
pinebook
pinephone
pinetab
sopine_baseboard
teres_i
p2371-2180

# armel
dockstar
dreamplug
guruplug
sheevaplug
rpi
rpi_0_w

# armhf
arndale
odroid
odroid-xu3
colibri_imx6
dh_imx6
mx53loco
mx6cuboxi
mx6qsabrelite
nitrogen6q
novena
novena-rawsd
udoo
usbarmory
wandboard
am335x_boneblack
am335x_evm
am57xx_evm
dra7xx_evm
igep00x0
nokia_rx51
omap3_beagle
omap4_panda
firefly-rk3288
rpi_2
rpi_3_32b
rpi_4_32b
stm32mp157c-dk2
A10-OLinuXino-Lime
A10s-OLinuXino-M
A20-OLinuXino-Lime
A20-OLinuXino-Lime2
A20-OLinuXino-Lime2-eMMC
A20-OLinuXino_MICRO
A20-OLinuXino_MICRO-eMMC
A20-Olimex-SOM-EVB
Bananapi
Bananapi_M2_Ultra
Bananapro
CHIP
Cubieboard
Cubieboard2
Cubieboard4
Cubietruck
Cubietruck_plus
Lamobo_R1
Linksprite_pcDuino
Linksprite_pcDuino3
Mini-X
Sinovoip_BPI_M3
bananapi_m2_berry
nanopi_neo
nanopi_neo_air
orangepi_plus
orangepi_zero
jetson-tk1


Thanks!


live well,
  vagrant

[toc] | [next] | [standalone]


#1130576 — Bug#1016963: Please test u-boot for rpi_3 rpi_3_32b

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:10 +0100
SubjectBug#1016963: Please test u-boot for rpi_3 rpi_3_32b
Message-ID<FHOEF-dYMu-1@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

rpi_3
rpi_3_32b

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130579 — Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:20 +0100
SubjectBug#1016963: Please test u-boot for rpi_4 rpi_4_32b
Message-ID<FHOOl-dYQ9-5@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

rpi_4
rpi_4_32b

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130580 — Bug#1016963: Please test u-boot for rpi_4 bananapi_m2_berry rpi_4_32b

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:20 +0100
SubjectBug#1016963: Please test u-boot for rpi_4 bananapi_m2_berry rpi_4_32b
Message-ID<FHOOl-dYQ9-11@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

rpi_4
bananapi_m2_berry
rpi_4_32b

[toc] | [prev] | [next] | [standalone]


#1130581 — Bug#1016963: Please test u-boot for orangepi_one_plus

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:30 +0100
SubjectBug#1016963: Please test u-boot for orangepi_one_plus
Message-ID<FHOY1-dYTw-1@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

orangepi_one_plus

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130582 — Bug#1016963: Please test u-boot for colibri_imx6

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:40 +0100
SubjectBug#1016963: Please test u-boot for colibri_imx6
Message-ID<FHP7I-dYXu-3@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

colibri_imx6

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130583 — Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:40 +0100
SubjectBug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck
Message-ID<FHP7I-dYXu-7@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

dreamplug
jetson-tk1
Bananapi
Cubieboard2	
Cubietruck

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130650 — Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck

FromIan Campbell <ijc@debian.org>
Date2022-12-29 13:30 +0100
SubjectBug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck
Message-ID<FI0cN-e6cv-3@gated-at.bofh.it>
In reply to#1130583
On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote:
> On 2022-12-28, Vagrant Cascadian wrote:
> > On 2022-12-22, Vagrant Cascadian wrote:
> > > On 2022-08-20, Vagrant Cascadian wrote:
> > > > On 2022-08-10, Vagrant Cascadian wrote:
> > > > > This bug is just to delay migration to testing while more
> > > > > platforms get
> > > > > tested. If you have a relevent board, please consider testing
> > > > > and
> > > > > reporting the status:
> > > > > 
> > > > >    https://wiki.debian.org/U-boot/Status
> > 
> > I have not received many test results for current or even remotely
> > recent u-boot platforms in Debian, and u-boot has been blocked from
> > migration to testing partly because of this.
> > 
> > As the bookworm freeze approaches, this is getting to be...
> > worrysome!
> > 
> > If you have access to any of these boards, please consider testing
> > u-boot versions as packaged in debian for versions from debian
> > stable
> > (2021.01*), testing (2022.04*), unstable (2022.10*) and
> > experimental
> > (2023.01-rc*) and updating the wiki page if successful and/or
> > replying
> > to 1016963@bugs.debian.org with a positive confirmation...
> > 
> > ...and if not successful, filing bugs against the relevent u-boot-*
> > packages and marking them as blocking 1016963.
> 
> dreamplug

booting u-boot and Debian both from external mmc

 testing: 2022.04+dfsg-2+b1  "FDT and ATAGS support not compiled in" then resets and loops doing that
unstable: 2022.10+dfsg-2     ok
     exp: 2023.01~rc4+dfsg-1 ok

comparing the config of 2022.04+dfsg-2+b1 vs 2022.10+dfsg-2 I see:

   -# CONFIG_SUPPORT_PASSING_ATAGS is not set
   +# CONFIG_ARCH_GXP is not set
   +CONFIG_SUPPORT_PASSING_ATAGS=y
   +CONFIG_SETUP_MEMORY_TAGS=y
   +CONFIG_CMDLINE_TAG=y
   +CONFIG_INITRD_TAG=y
   
which I suspect explains the failure in 2022.04+dfsg-2+b1.

> jetson-tk1
> Bananapi
> Cubieboard2     

I have these somewhere, I think in a box in the loft, I have to go up
there later anyway so will see if I can find any of them.

> Cubietruck

u-boot on mmc + Debian on sata:

 testing: 2022.04+dfsg-2+b1  ok
unstable: 2022.10+dfsg-2     ok
     exp: 2023.01~rc4+dfsg-1 ok

I've updated the wiki with the 5 successes, I didn't update the
dreamplug testing entry nor file a bug, I assume 2022.10+dfsg-2 will
eventually be allowed to migrate to fix that issue.


Ian.

[toc] | [prev] | [next] | [standalone]


#1134245 — Bug#1016963: Please test u-boot for dreamplug

FromVagrant Cascadian <vagrant@debian.org>
Date2023-01-21 21:20 +0100
SubjectBug#1016963: Please test u-boot for dreamplug
Message-ID<FQsvf-bmq-1@gated-at.bofh.it>
In reply to#1130650

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-29, Ian Campbell wrote:
> On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote:
>> dreamplug
>
> booting u-boot and Debian both from external mmc
>
>  testing: 2022.04+dfsg-2+b1  "FDT and ATAGS support not compiled in" then resets and loops doing that
> unstable: 2022.10+dfsg-2     ok
>      exp: 2023.01~rc4+dfsg-1 ok

Any chance you could test 2023.01+dfsg-1 and/or 2023.01+dfsg-2 on the
dreamplug? Someone had problems with sheevaplug, which I think is a
fairly similar platform.

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1134318 — Bug#1016963: Please test u-boot for dreamplug

FromIan Campbell <ijc@debian.org>
Date2023-01-22 10:00 +0100
SubjectBug#1016963: Please test u-boot for dreamplug
Message-ID<FQEmK-iOQ-3@gated-at.bofh.it>
In reply to#1134245
On Sat, 2023-01-21 at 12:09 -0800, Vagrant Cascadian wrote:
> On 2022-12-29, Ian Campbell wrote:
> > On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote:
> > > dreamplug
> > 
> > booting u-boot and Debian both from external mmc
> > 
> >   testing: 2022.04+dfsg-2+b1  "FDT and ATAGS support not compiled
> > in" then resets and loops doing that
> > unstable: 2022.10+dfsg-2     ok
> >       exp: 2023.01~rc4+dfsg-1 ok
> 
> Any chance you could test 2023.01+dfsg-1 and/or 2023.01+dfsg-2 on the
> dreamplug? Someone had problems with sheevaplug, which I think is a
> fairly similar platform.

Done, both versions worked fine on dreamplug.

I also think dreamplug is a fairly similar platform to sheevaplug, but
I have no personal experience of the latter.

Ian.

[toc] | [prev] | [next] | [standalone]


#1130671 — Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck

FromIan Campbell <ijc@debian.org>
Date2022-12-29 18:10 +0100
SubjectBug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck
Message-ID<FI4zL-e92A-11@gated-at.bofh.it>
In reply to#1130583
On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote:
> jetson-tk1

 testing: 2022.04+dfsg-2+b1  ok
unstable: 2022.10+dfsg-2     ok
     exp: 2023.01~rc4+dfsg-1 ok

> Bananapi

I don't seem to have a working setup for this any more, sorry.

> Cubieboard2     

 testing: 2022.04+dfsg-2+b1  ok
unstable: 2022.10+dfsg-2     ok
     exp: 2023.01~rc4+dfsg-1 ok

I mentioned those successes on the wiki.

[toc] | [prev] | [next] | [standalone]


#1130584 — Bug#1016963: Please test u-boot for dh_imx6

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:40 +0100
SubjectBug#1016963: Please test u-boot for dh_imx6
Message-ID<FHP7I-dYXu-9@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

dh_imx6

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130585 — Bug#1016963: Please test u-boot for sheevaplug mx6cuboxi

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:40 +0100
SubjectBug#1016963: Please test u-boot for sheevaplug mx6cuboxi
Message-ID<FHP7I-dYXu-15@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

sheevaplug
mx6cuboxi

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130586 — Bug#1016963: Please test u-boot for am335x_boneblack am335x_evm

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:50 +0100
SubjectBug#1016963: Please test u-boot for am335x_boneblack am335x_evm
Message-ID<FHPhn-dZ1q-3@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

am335x_boneblack
am335x_evm

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130587 — Bug#1016963: Please test u-boot for nitrogen6q sifive_unleashed

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:50 +0100
SubjectBug#1016963: Please test u-boot for nitrogen6q sifive_unleashed
Message-ID<FHPho-dZ1q-11@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

nitrogen6q
sifive_unleashed

I'm able to test sifive_unmatched myself, but more people testing the
better.

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130588 — Bug#1016963: Please test u-boot for mx53loco wandboard igep00x0 omap3_beagle omap4_panda Cubietruck

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 01:50 +0100
SubjectBug#1016963: Please test u-boot for mx53loco wandboard igep00x0 omap3_beagle omap4_panda Cubietruck
Message-ID<FHPho-dZ1q-15@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

mx53loco
wandboard
igep00x0
omap3_beagle
omap4_panda
Cubietruck

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130589 — Bug#1016963: Please test u-boot for Linksprite_pcDuino

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 02:00 +0100
SubjectBug#1016963: Please test u-boot for Linksprite_pcDuino
Message-ID<FHPr4-dZ5o-3@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

Linksprite_pcDuino

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130590 — Bug#1016963: Please test u-boot for A20-OLinuXino_MICRO-eMMC

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 02:00 +0100
SubjectBug#1016963: Please test u-boot for A20-OLinuXino_MICRO-eMMC
Message-ID<FHPr4-dZ5o-5@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

A20-OLinuXino_MICRO-eMMC

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1130591 — Bug#1016963: Please test u-boot for Mini-X

FromVagrant Cascadian <vagrant@debian.org>
Date2022-12-29 02:00 +0100
SubjectBug#1016963: Please test u-boot for Mini-X
Message-ID<FHPr4-dZ5o-7@gated-at.bofh.it>
In reply to#1130571

[Multipart message — attachments visible in raw view] — view raw

On 2022-12-28, Vagrant Cascadian wrote:
> On 2022-12-22, Vagrant Cascadian wrote:
>> On 2022-08-20, Vagrant Cascadian wrote:
>>> On 2022-08-10, Vagrant Cascadian wrote:
>>>> This bug is just to delay migration to testing while more platforms get
>>>> tested. If you have a relevent board, please consider testing and
>>>> reporting the status:
>>>>
>>>>   https://wiki.debian.org/U-boot/Status
>
> I have not received many test results for current or even remotely
> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
>
> If you have access to any of these boards, please consider testing
> u-boot versions as packaged in debian for versions from debian stable
> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
> (2023.01-rc*) and updating the wiki page if successful and/or replying
> to 1016963@bugs.debian.org with a positive confirmation...
>
> ...and if not successful, filing bugs against the relevent u-boot-*
> packages and marking them as blocking 1016963.

Mini-X

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]


#1131727 — Bug#1016963: Please test u-boot for Mini-X

FromJochen Sprickerhof <jspricke@debian.org>
Date2023-01-04 23:40 +0100
SubjectBug#1016963: Please test u-boot for Mini-X
Message-ID<FKkAp-fBTo-1@gated-at.bofh.it>
In reply to#1130591

[Multipart message — attachments visible in raw view] — view raw

Hi Vagrant,

* Vagrant Cascadian <vagrant@debian.org> [2022-12-28 16:56]:
>>>>> This bug is just to delay migration to testing while more platforms get
>>>>> tested. If you have a relevent board, please consider testing and
>>>>> reporting the status:
>>>>>
>>>>>   https://wiki.debian.org/U-boot/Status
>>
>> I have not received many test results for current or even remotely
>> recent u-boot platforms in Debian, and u-boot has been blocked from
>> migration to testing partly because of this.
>>
>> As the bookworm freeze approaches, this is getting to be... worrysome!
>>
>> If you have access to any of these boards, please consider testing
>> u-boot versions as packaged in debian for versions from debian stable
>> (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
>> (2023.01-rc*) and updating the wiki page if successful and/or replying
>> to 1016963@bugs.debian.org with a positive confirmation...
>>
>> ...and if not successful, filing bugs against the relevent u-boot-*
>> packages and marking them as blocking 1016963.
>
>Mini-X

Works fine with unstable, I've updated the wiki page.

Cheers Jochen

[toc] | [prev] | [next] | [standalone]


Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.bugs.dist


csiph-web