The move from dracut 059 to 060 led to some additional modules being
in the initrd. A workaround is to add a dracut config snippet that
includes the firmware in the initrd. after putting the file in
/etc/dracut.conf.d/ you will need to rebuild the initrd. ideally the
driver should try and reload
Does anyone have an alternate email for Konstantin Porotchkin? he is
listed as the maintainer for theESPRESSOBin BOARD. and his email is
bouncing because his inbox is full.
Dennis
On Mon, Apr 1, 2024 at 8:40 PM Dennis Gilmore wrote:
>
> While preboot was enabled, it did not work as co
-off-by: Dennis Gilmore
---
configs/mvebu_espressobin-88f3720_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/mvebu_espressobin-88f3720_defconfig
b/configs/mvebu_espressobin-88f3720_defconfig
index 7ecf5ab0d64..f4f7a809609 100644
--- a/configs/mvebu_espressobin
helios4_defconfig
> +++ b/configs/helios4_defconfig
> @@ -44,7 +44,6 @@ CONFIG_CMD_MMC=y
> CONFIG_CMD_PCI=y
> CONFIG_CMD_SPI=y
> CONFIG_CMD_USB=y
> -# CONFIG_CMD_SETEXPR is not set
> CONFIG_CMD_TFTPPUT=y
> CONFIG_CMD_CACHE=y
> CONFIG_CMD_TIME=y
>
> --
> 2.35.
On Fri, 9 Feb 2024, 04:52 Peter Boy, wrote:
> Nowadays several SBC devices provide eMMC storage soldered and no longer
> removable. How to install on this?
>
>
> My first idea was to first install on mSD card, boot, and from this repeat
> the installation with the eMMC target. But this doesn’t
> kernel modules and configurations (along with various other sources) to come
> up with my "ultimate" configuration from my first e-mail thread.
>
> I am at a complete loss. Fedora seems to work on the X13s for everyone except
> me.
>
> Sincerely,
> Luke Short
to get pd-mapper to work you need to remove
/etc/modprobe.d/anaconda-denylist.conf and regenerate the initrd. you
can modprobe qcom_q6v5_pas and then start pd-mapper to get battery
reporting working without a reboot
On Sat, Dec 16, 2023 at 4:17 PM Dennis Gilmore wrote:
>
> Hi Luke,
>
oller: sync_state()
> pending due to 3000.remoteproc
> [ 12.] qcom-rpmhpd 1820.rsc:power-controller: sync_state()
> pending due to 3d90.clock-controller
> [ 12.] qcom-rpmhpd 1820.rsc:power-controller: sync_state()
> pending due to 894000.i2c
> [ 12.]
On Tue, Dec 12, 2023 at 10:01 PM Luke Short wrote:
>
> Hey folks,
>
> I recently purchased the X13s Qualcomm Arm laptop. I am very excited to try
> Linux on it! I'd like to use Fedora to align with what I use for work. The
> [Fedora Wiki](https://fedoraproject.org/wiki/Thinkpad_X13s) page
A big benefit of using the full dtb in u-boot means it can be used to
boot the system without the need to load a replacement file from disk
or elsewhere, which, AFAIK is required for the System Ready standards
and it definitely helps in cases like EFI booting.
Dennis
On Wed, Nov 29, 2023 at
On Thu, Nov 23, 2023 at 6:51 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Wed, Nov 22, 2023 at 01:53:14PM +0100, Gerd Hoffmann wrote:
> > On Tue, Nov 21, 2023 at 08:07:06AM -0800, Davide Cavalca wrote:
> > > On 2023-11-21 04:34, Jiri Konecny wrote:
> > > > Is Anaconda Initial Setup important for
On Mon, Nov 27, 2023 at 7:53 AM Neal Gompa wrote:
>
> On Mon, Nov 27, 2023 at 8:13 AM wrote:
> >
> > On Fri, 2023-11-24 at 15:15 -0800, Adam Williamson wrote:
> > > On Tue, 2023-11-21 at 13:34 +0100, Jiri Konecny wrote:
> > > > Hello everyone,
> > > >
> > > > Is Anaconda Initial Setup important
All of the Arm disk images use initial-setup to configure the image.
There would need to a concrete plan on how to manage the transition to
something else.
Dennis
On Tue, Nov 21, 2023 at 6:35 AM Jiri Konecny wrote:
>
> Hello everyone,
>
> We (anaconda team) are considering discontinuation of
All of the Arm disk images use initial-setup to configure the image.
There would need to a concrete plan on how to manage the transition to
something else.
Dennis
On Tue, Nov 21, 2023 at 6:35 AM Jiri Konecny wrote:
>
> Hello everyone,
>
> We (anaconda team) are considering discontinuation of
On Tue, Aug 22, 2023 at 9:34 AM Shengyu Qu wrote:
> Since PLDA PCIE driver is added and VL805 support is enabled in
> defconfig for Starfive Visionfive 2, modify the document to keep
> consistent.
>
> Signed-off-by: Shengyu Qu
>
Tested-by: Dennis Gilmore
> ---
SB subsystem and scan nvme drive on boot.
>
> Signed-off-by: Shengyu Qu
>
Tested-by: Dennis Gilmore
> ---
> configs/starfive_visionfive2_defconfig | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/configs/starfive_visionfive2_defconfig
> b
I think it is fair to say it is a system wide change
Dennis
On Wed, Aug 2, 2023 at 1:40 PM Amit Shah wrote:
>
>
> On Wed, 2023-08-02 at 10:50 -0500, Dennis Gilmore via devel wrote:
> > Given https://fedoraproject.org/wiki/Changes/BINUTILS_GOLD and
> > https://fedoraproj
Given https://fedoraproject.org/wiki/Changes/BINUTILS_GOLD and
https://fedoraproject.org/wiki/Features/GoldLinkerDefault it seems
reasonable that to remove the feature we have a change to ensure wide
notice and documentation of the change
Dennis
On Wed, Jun 21, 2023 at 10:08 AM Amit Shah wrote:
I am just running the Fedora kernel, I have not tried to do anything with
Cuda
On Thu, May 11, 2023 at 7:01 PM Mario Marietto
wrote:
> Im trying to upgrade cuda 10 to 11 and try to use kernel 5.x. Which CUDA /
> kernel versions are running on your nanos ?
>
> Il ven 12 mag 2023,
I have 3 x 4GiB Jetson Nano's. I have updated the u-boot on them using the
update documentation provided, I did put the fedora build u-boot binary in
place and flashed that. I am running Fedora Server on them all. 2 of them
are running freeipa and are my local dns servers, the third I run DHCP and
On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson
wrote:
> "
>
> On Wed, Mar 29, 2023 at 6:18 PM Peter Boy wrote:
> >
> >
> >
> > > Am 28.03.2023 um 14:09 schrieb Peter Robinson :
> > >
> > > Yes, it's a known problem, it will be fixed with the U-Boot rc5 build
> > > which should be done later
On Thu, Mar 9, 2023 at 7:37 AM Fabio Valentini wrote:
> Hi all,
>
> As a follow-up from a recent discussion on Matrix/IRC, I'm proposing
> the following change to the development cycle / release schedule:
>
> "Koji builds are blocked while mass branching and updates-testing
> enablement are in
On Tue, Feb 21, 2023 at 2:48 PM Matthew Miller
wrote:
> I was asked to weigh in on https://pagure.io/releng/issue/7215 as a
> priority. Last time we talked about this we didn't really get anywhere...
>
>
>
On Mon, Jan 30, 2023 at 3:05 PM Kevin Fenzi wrote:
> Greetings everyone.
>
> I've been working on migrating things to rhel9 of late.
> I reinstalled a staging virthost or two and found that while rhel8 would
> allow /boot and /boot/efi to be on raid, rhel9 does not all this at all.
>
Fedora
On Thu, Dec 22, 2022 at 5:25 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Wed, Dec 21, 2022 at 11:56:32AM -0600, Dennis Gilmore via devel wrote:
> > In my case, I have Network Manager config files included in my initrd
> > and bootargs to bring up the network so that I
In my case, I have Network Manager config files included in my initrd
and bootargs to bring up the network so that I get automatic disk
decryption while on my home network, and prompted for a password when
I am not at home. I think this a reasonable enough use case it should
be considered in the
appending amdgpu.runpm=0 to the bootargs, it was a suggestion as I
have to append pcie_aspm=off. I get further, and despite a lot of
noise X starts
[ 19.501645] [drm] amdgpu kernel modesetting enabled.
[ 19.515932] amdgpu: CRAT table disabled by module option
[ 19.522205] amdgpu: IO link
I have an Ampere Altra machine that I have put a Radeon 6500 XT card
on seeing the pull request for drm-next-6.2
https://lore.kernel.org/dri-devel/20221104205827.6008-1-alexander.deuc...@amd.com/
I grabbed the tree and built it. On boot I am getting
[ 23.877255] [drm] amdgpu kernel modesetting
I have an Ampere Altra machine that I have put a Radeon 6500 XT card
on seeing the pull request for drm-next-6.2
https://lore.kernel.org/dri-devel/20221104205827.6008-1-alexander.deuc...@amd.com/
I grabbed the tree and built it. On boot I am getting
[ 23.877255] [drm] amdgpu kernel modesetting
# dnf --releasever=37 --setopt=module_platform_id=platform:f37
--enablerepo=updates-testing $(rpm -q fedora-repos-modular >/dev/null
&& echo --enablerepo=updates-testing-modular) --assumeno distro-sync
Fedora 37 - x86_64
22 MB/s |
81 MB
On Sun, Feb 6, 2022 at 7:55 AM David Bold wrote:
>
> On 11/15/21 20:15, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/RetireARMv7
> >
> ...
> > == Scope ==
> >
> > * Proposal owners: Work with rel-eng to disable the architecture in
> > koji, remove all the various pungi pieces and
Adding count probably cut the image short, it is not necessary, I generally
always us bs=4MiB
Dennis
On Sun, Jan 9, 2022, 03:54 David W. Legg wrote:
> Well, I copied the card from the 2GB rpi4 using:
>
> dd if=/dev/sdf of=card.img bs=1M count=9000 status=progress
>
> and wrote another card
Try running "echo 110 > /sys/class/hwmon/hwmon1/pwm1" then bump it back to
255 I have found that to work on a different rockchip based device
Dennis
On Tue, Dec 7, 2021, 05:30 Peter Robinson wrote:
> > The fan on my Rockpro64 does not work with fedora 34 installed. The
> > file
On Wed, Aug 18, 2021 at 3:11 PM Florian Weimer wrote:
>
> * Dennis Gilmore:
>
> > We intentionally never looked at enabling that and always had no plans
> > to support multi-lib on Arm
>
> It's not multilib. Buildroots aren't multilib.
>
> I'm pretty sure no one
On Mon, Aug 16, 2021 at 12:55 AM Florian Weimer wrote:
>
> * Kevin Fenzi:
>
> > On Sun, Aug 15, 2021 at 01:51:16PM +0200, Florian Weimer wrote:
> >> * Kevin Fenzi:
> >>
> >> > Yes. They were mistakenly running the normal kernel (so they had ~3GB
> >> > memory available). I moved them back to the
On Sat, Jul 24, 2021 at 11:03 AM Tom Rini wrote:
>
> On Fri, Jul 23, 2021 at 10:49:39PM -0500, Dennis Gilmore wrote:
> > On Fri, Jul 23, 2021 at 10:25 PM Tom Rini wrote:
> > >
> > > On Fri, Jul 23, 2021 at 09:46:44PM -0500, Dennis Gilmore wrote:
>
On Fri, Jul 23, 2021 at 10:25 PM Tom Rini wrote:
>
> On Fri, Jul 23, 2021 at 09:46:44PM -0500, Dennis Gilmore wrote:
>
> > removing the header is not sufficient to have the boards booting from SPI.
> >
> > U-Boot TPL 2021.07-00768-g49373a3334-dirty (Jul 23 2021 - 20:4
removing the header is not sufficient to have the boards booting from SPI.
U-Boot TPL 2021.07-00768-g49373a3334-dirty (Jul 23 2021 - 20:42:57)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die
I am not sure if it impacts non rk3399 devices or not, but on at least
rk3399 devices after
https://source.denx.de/u-boot/u-boot/-/commit/346df7d4fa62afc578d820b3a18815eec765074f
was applied installing u-boot into SPI flash results in an unbootable
system. SPL loads and runs, u-boot.itb is not
On Wed, Jul 21, 2021 at 3:53 PM Richard W.M. Jones wrote:
>
> On Wed, Jul 21, 2021 at 01:52:26PM +0200, Tomas Hrcka wrote:
> >
> >
> > Can the packagers fix the failures in the f35-rebuild side tag by
> > themselves
> > while the rebuild is in progress, or do they have to wait on
From: Dennis Gilmore
This is a stripped down version of the vendor U-Boot patch by Aditya
Prayoga found in the armbian repository. This patch is enough to have
the 1G ethernet port, the micro SD card, eMMC, PCIe and UART. It sets
uart2 as the default outiput device. the defconfig file has been
I have been working on an updated version, I have cleaned up the
config a lot as well as done some work to make the -u-boot.dtsi file
smaller
https://pagure.io/u-boot/c/2472db2eff8ba0fb262a0d0264aa9d9c7b3eca32?branch=helios64
is my current WIP patch, I have built it on top of updating the base
some of the changes have just been committed already, or an equivalent.
The value you have for the license is incorrect
https://fedoraproject.org/wiki/Licensing:Main lists the correct values
-License:LGPL-2.1
+License:LGPLv2
There is no need to explicitly Require
you probably sent the same srpm,
https://koji.fedoraproject.org/koji/taskinfo?taskID=2020 builds
just fine, I did make a few changes to the spec file. with a correct
changelag entry it should pass review
Dennis
On Sun, Apr 25, 2021 at 8:58 AM Joan Moreau via devel
wrote:
>
> Same status :(
On Sun, Apr 25, 2021 at 8:48 AM Richard Shaw wrote:
>
> On Sun, Apr 25, 2021 at 8:36 AM Joan Moreau via devel
> wrote:
>>
>> When I launch the "koji" comand, build fails because it does not find g++
>>
>> (see :
>> https://kojipkgs.fedoraproject.org//work/tasks/9140/66659140/build.log )
>>
>>
On Fri, Apr 23, 2021, 09:14 Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:
> On Friday, 23 April 2021 at 15:49, Dennis Gilmore wrote:
> > On Fri, Apr 23, 2021 at 7:14 AM Dominik 'Rathann' Mierzejewski
> > wrote:
> > >
> > > On Thursday, 22
perhaps you should look at how ceph has dealt with a similar issue,
they set the max number of cpus based on the system ram.
https://src.fedoraproject.org/rpms/ceph/blob/rawhide/f/ceph.spec#_1246
Dennis
On Fri, Mar 26, 2021 at 7:49 PM Michel Alexandre Salim
wrote:
>
> Hi all,
>
> This idea came
On Mon, 2021-03-08 at 19:07 +0100, Miro Hrončok wrote:
> On 08. 03. 21 18:33, Mattia Verga via devel wrote:
> > I'm just wondering: what's the benefit of packaging Python noarch
> > projects in Fedora?
>
> You can use them as requirements for packaged applications.
>
> > I can see the reason
Hi Uwe,
Not all of the new files have SPDX headers as well. There was a second
submission of this patch set this week. Perhaps you can work with
Christian on the support?
Dennis
On Sat, Feb 27, 2021 at 9:32 PM Dennis Gilmore
wrote:
>
> On Fri, Feb 26, 2021 at 12:57 AM Uwe Kleine
Uwe submitted this board last Thursday
Dennis
On Tue, Mar 2, 2021 at 10:46 AM Christian Glombek
wrote:
>
> The hardware is described in detail on Kobol's wiki at
> https://wiki.kobol.io/helios64/intro/.
>
> This commit is based on downstream work in Armbian by Aditya Prayoga [1].
> The
On Fri, Feb 26, 2021 at 12:57 AM Uwe Kleine-König
wrote:
>
> Hi Dennis,
>
> thanks for your feedback.
>
> On 2/26/21 12:23 AM, Dennis Gilmore wrote:
> > Thanks for submitting, I have been meaning to do so myself, I have
> > been meaning to go through and try
Thanks for submitting, I have been meaning to do so myself, I have
been meaning to go through and try get the dts files in a decent
shape. I think that most of what is in
arch/arm/dts/rk3399-kobol-helios64-u-boot.dtsi belongs in
arch/arm/dts/rk3399-kobol-helios64.dts I also wonder if we shouldn't
yum distro-sync --releasever 34
Last metadata expiration check: 0:10:11 ago on Wed 24 Feb 2021 11:55:46 AM CST.
Error:
Problem: package gnome-tour-40~beta-3.fc34.x86_64 obsoletes
gnome-getting-started-docs < 3.38.1-2 provided by
gnome-getting-started-docs-3.38.0-2.fc34.noarch
- package
The u-boot images in Fedora for the RockPro64 are for mmc only, you
need to install it into the sdcard and boot from that. there is
currently no images to install in SPI
Dennis
On Tue, Feb 16, 2021 at 12:09 PM Marcin Juszkiewicz
wrote:
>
> W dniu 16.02.2021 o 18:50, Aaron Siegel pisze:
> >
could I please get someone to review this patch
Dennis
On Tue, Dec 8, 2020 at 9:07 PM wrote:
>
> From: Dennis Gilmore
>
> Move all aliases defintions into the main dts file
> Add u-boot definiton to i2c0 based on clearfog
> set spi1 status to okay
>
> Signe
Hi Stefano,
I really do not think that this patch should have been merged. It is
not the preferred way to boot distros and is left in for legacy
support only. We probably should make it as such.
Dennis
On Sat, Jan 23, 2021 at 9:53 AM wrote:
>
> > From: Alice Guo
> > Distro Boot requires a
boot.scr is only in distro boot because prior to standardising in
extlinux.conf or grub vie efi, distros provided boot.scr files that
were tailored for each board with detailed staps and memory locations
to load the kernel, dtb, and initramfs. the scripts were wrapped by
mkimage and at this point
Tested-by: Dennis Gilmore
On Fri, 2020-12-11 at 05:47 +0100, Stefan Roese wrote:
> For correct spi bus detection the spi0 alias is needed in the DT.
> Otherwise this error will ocurr in U-Boot:
>
> Invalid bus 0 (err=-19)
> Failed to initialize SPI flash at 0:0 (error -19)
Tested-by: Dennis Gilmore
On Thu, 2020-12-10 at 06:40 +0100, Stefan Roese wrote:
> Add some missing "u-boot,dm-pre-reloc;" properties to UART0, SPI
> controller and SPI NOR flash node to enable usage in SPL. Otherwise
> these devices will not be available.
>
> Signed-o
okay";
> + u-boot,dm-pre-reloc;
with this dts change the serial port is registered correctly
Dennis
> };
> serial@12100 {
> status = "okay";
>
>
> Thanks,
> Stefan
>
--
Dennis Gilmore
Multiple Architecture Portfolio Enablement
T: +1-312-660-3523
Hi all,
I filed https://pagure.io/fesco/issue/2512 asking FESCo to move all
automated emails to a separate list where people who want to follow
can, while I was part of the proliferation of compose reports coming
here, there is now a great deal of them, and they no longer seem to
trigger any
It would require https://bugzilla.redhat.com/show_bug.cgi?id=1768206
to be fixed. Right now the design in dnf for supporting gpg keys is
quite user hostile, especially in automated unattended use cases.
Dennis
On Mon, Nov 2, 2020 at 6:25 PM Marek Marczykowski-Górecki
wrote:
>
> Hello all,
>
>
u-boot also supports pxe booting using a syslinux config file
https://github.com/u-boot/u-boot/blob/master/doc/README.pxe
Dennis
On Tue, Sep 15, 2020 at 5:43 PM Heinrich Schuchardt wrote:
>
> On 9/1/20 2:49 PM, Ahsan Zia (TAU) wrote:
> > Hi All,
> >
> > I need some ideas regarding Boot Over
I agree with Tom here, I have a few different systems that use this
feature, it is useful. I think most if not all of the systems I have
using it have Marvell SoC's
Dennis
On Fri, Sep 11, 2020 at 12:11 PM Tom Rini wrote:
>
> On Fri, Sep 11, 2020 at 06:47:02PM +0200, Andre Heider wrote:
> > On
On Thu, Sep 3, 2020 at 3:24 PM Stephen Warren wrote:
>
> On 9/3/20 2:14 PM, Dennis Gilmore wrote:
> > On Thu, Sep 3, 2020 at 2:15 PM Stephen Warren wrote:
> >>
> >> On 9/3/20 10:40 AM, Dennis Gilmore wrote:
> >>> When testing builds provided in
> >
On Thu, Sep 3, 2020 at 2:15 PM Stephen Warren wrote:
>
> On 9/3/20 10:40 AM, Dennis Gilmore wrote:
> > When testing builds provided in https://github.com/openwrt/openwrt/pull/3360
> > I discovered that fdtfile was not set and as a result the firmware was not
> > functio
When testing builds provided in https://github.com/openwrt/openwrt/pull/3360
I discovered that fdtfile was not set and as a result the firmware was not
functional. So I am documenting what is needed.
Signed-off-by: Dennis Gilmore
Cc: Atish Patra
Cc: Lukas Auer
Cc: Tom Rini
Cc: Masahiro
Simon,
Is there a way to replace the firmware on those boards with u-boot? I
have a Tegra, a rockchip, and a pair of Samsung Exynos based
Chromebooks that are end of life for ChromeOS but are still quite
useful hardware platforms if there was a way to replace entirely the
bootloader with u-boot
This is very sad news, he was a very enthusiastic tester.
Dennis
On Sun, Aug 2, 2020 at 5:49 PM Adam Williamson
wrote:
>
> Hi, folks. I'm sad to report that Thomas Gilliard (satellit), who was a
> valued member of the QA team for many years, passed away last week. His
> wife contacted me with
likely the device tree file needs to have the wif device added for it
to show up.
Dennis
On Tue, Jul 21, 2020 at 9:19 PM brm wrote:
>
> Hi all. OS is 5.7.8-200.fc32.aarch64 Fedora Server running headless on Pine64
> sbc. The system works well. Currently eth0 is the main network device, but I
>
Just like there is many different dialects of Spanish, and other
languages the same is true of English, many parts of the language are
shared, and the most critical part for most people is making sure that
things like Paper settings, date, and number formats are correct for
their location. It is
resending from a different email address as Gmail rejected my first
attempt to send
On Sat, Apr 18, 2020 at 9:18 AM Dennis Gilmore
wrote:
>
> On Fri, Apr 17, 2020 at 2:19 AM Joel Johnson wrote:
> >
> > Update mvebu SPL boot selection mechanism for the move to driver model
>
Hi all,
before going off an filing a bug, I wanted to gather some input. I
added a battery for the RTC to one of my ARM boards, in testing that
it was working as expected I booted the system I noticed the following
[root@localhost ~]# date
Wed 01 Apr 2020 05:24:35 PM UTC
[root@localhost ~]#
Hi Jeffrey,
Feel free to reach out to me on freenode (dgilmore), I do not have a
huge amount of time but I can help you get started in working on
u-boot. We have a mostly upstream u-boot and work to get all patches
upstream. Getting engaged upstream will also be a necessary step.
Dennis
On Sat,
I would honestly say it is probably fine to remove them. You could just use
a Fedora container to get what you need if you are working on reproducible
builds and need to provide some support. Though as Neal said it shouldn't
be too hard to update everything, Fedora is well on the way to removing
I would honestly say it is probably fine to remove them. You could just use
a Fedora container to get what you need if you are working on reproducible
builds and need to provide some support. Though as Neal said it shouldn't
be too hard to update everything, Fedora is well on the way to removing
`koji list-api`
provides full documentation of the API
Dennis
On Fri, Oct 25, 2019 at 9:20 AM Miroslav Suchý wrote:
>
> Hi.
> I cannot find documentation for Koji API. Can someone help me where I can
> find it?
> --
> Miroslav Suchy, RHCA
> Red Hat, Associate Manager ABRT/Copr, #brno,
On Fri, Oct 4, 2019 at 6:30 AM Richard W.M. Jones wrote:
>
>
> This has happened to me twice this morning, the second time here:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=38048038
>
> Rich.
koji uses very simple logic in parsing mock return codes
As you are adding no Fedora content you must use different branding
https://fedoraproject.org/wiki/Legal:Trademark_guidelines#Secondary_Mark
you are free to make your own release package and put content as you want
to.
Dennis
On Wed, Sep 11, 2019, 05:25 Danishka Navin wrote:
> Is it ok to
There was issues identified with 32 bit ceph and upstream stopped
supporting 32 bit arches entirely.
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/XCQIMO3W3D5XGHQHBVVIBUBPIXKJJJWL/
has all the details and discussion on it.
Dennis
On Tue, Jul 23, 2019, 15:39
On Thu, Jun 6, 2019 at 7:11 AM Neal Gompa wrote:
>
> On Thu, Jun 6, 2019 at 7:53 AM Florian Weimer wrote:
> >
> > Is there a reason why we do not tag dist-git commits, using a name which
> > is derived from the NEVR from a Koji build?
> >
> > How well does Git scale with thousands of tags?
> >
>
Reviewed-by: Dennis Gilmore
Tested-by: Dennis Gilmore
On Mon, May 20, 2019 at 2:53 AM Stefan Roese wrote:
>
> This patch enables CONFIG_BLK and CONFIG_DM_MMC on helios4 to remove
> these compile warnings:
>
> = WARNING ==
> This
On Fri, May 17, 2019 at 7:24 AM Stephen Gallagher wrote:
>
> On Thu, May 16, 2019 at 2:54 PM Ben Cotton wrote:
> >
> > https://fedoraproject.org/wiki/Changes/DisableRootPasswordLoginInSshd
> >
> > == Summary ==
> > The upstream OpenSSH disabled password logins for root back in 2015.
> > The
On Thu, May 9, 2019 at 10:22 AM Jun Aruga wrote:
>
> Kevin and Clement, thanks for the explanation.
>
> I am looking forward to seeing the final compose.
>
> > So, likely we haven't had a armv7 fedora 30 compose recently, and so no
> one has updated it. The container sig would be the ones to ask
https://www.openmainframeproject.org/ has some information on getting
access to mainframe resources. there is also some information at
https://osuosl.org/services/ibm-z/ I believe both of them end up
running on hardware at Marist brothers college. there is also some
info on how to use Jenkins for
On Thu, 2019-02-14 at 02:45 +0100, Tomasz Kłoczko wrote:
> Hi,
>
> Looks like MR which started two weeks ago still is not fully
> finished. Below command has been executed in mirrored rawhide source
> packages tree.
>
> [tkloczko@domek fedora]$ for i in fc{21..30}; do echo "$i $(ls -1
>
On Wed, 2019-01-23 at 16:13 +0800, Zamir Sun wrote:
> On Wed, Jan 23, 2019 at 12:08 PM Peter Robinson > wrote:
> > Hi,
> >
> > > I have a pinebook (running anarsoul's arch mainline[1]) and I was
> > > wondering if someone has tried Fedora 29 on the pinebook, or if
> > > it is even supported.
>
El lun, 07-01-2019 a las 15:21 +0100, arm...@rirasoft.de escribió:
> Am 2019-01-03 15:17, schrieb Dennis Gilmore:
> > El jue, 03-01-2019 a las 08:57 +0100, arm...@rirasoft.de escribió:
> > > Hello together and and happy and healthfull new year !
> > >
> > >
El jue, 03-01-2019 a las 08:57 +0100, arm...@rirasoft.de escribió:
> Hello together and and happy and healthfull new year !
>
> Yesterday the parcel with Helios 4 is be well received. Is there any
> hint to install Fedora (or maybe CentOS) on it?
>
> Greetings
> Andreas
Hi Andreas,
fedora
https://pagure.io/releng/issue/4084 its an issue that has existed for
nearly a decade and not been solved. Time was not taken to fixing it
after we disabled installing multilib by default as there was no
reports of it for years.
Dennis
El mié, 12-12-2018 a las 11:32 +0100, Florian Weimer
El vie, 14-12-2018 a las 20:33 +0100, Igor Gnatenko escribió:
> Hello folks,
>
> for long time we have problem if you have some arch-specific
> BuildRequires, you still get one src.rpm from one of arches (not sure
> how koji chooses that one) which might not work for your
> architecture.
>
> For
El mar, 04-12-2018 a las 16:14 -0500, Robert Moskowitz escribió:
>
> On 12/4/18 1:24 PM, Dennis Gilmore wrote:
> > The odroid boards need binary files we can not distribute. While I
> > have
> > a couple they are not really supportable.
>
> No success today. H
Series
Tested-By: Dennis Gilmore
Reviewed-By: Dennis Gilmore
El mié, 05-12-2018 a las 00:57 +0800, Aditya Prayoga escribió:
> Hi everyone,
>
> This series add some missing peripheral support and fixed that was
> implemented on U-Boot 2013.01 Marvell version: 2015_T1.0p16
> - hel
Tested-By: Dennis Gilmore
El mié, 05-12-2018 a las 00:39 +0800, Aditya Prayoga escribió:
> This patch add GPIO configuration support in mvneta driver.
> Driver will handle PHY reset. GPIO pins should be set in device tree.
>
> Ported from mvpp2x
> [https://patchwork.ozlabs.o
El mar, 04-12-2018 a las 13:12 -0500, Robert Moskowitz escribió:
>
> On 12/4/18 12:51 PM, Peter Robinson wrote:
> > On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz <
> > r...@htt-consult.com> wrote:
> > > Additional bug? in F28 x64 installer:
> > >
> > > # fedora-arm-image-installer
El jue, 29-11-2018 a las 00:42 +0700, Aditya Prayoga escribió:
> On Wed, Nov 28, 2018 at 8:44 PM Dennis Gilmore
> wrote:
> > On Wed, 2018-11-28 at 16:59 +0800, Aditya Prayoga wrote:
> > > Enable Marvell I2C driver and set default bus to external I2C
> > > bus.
>
On Wed, 2018-11-28 at 17:00 +0800, Aditya Prayoga wrote:
> Enable SPI flash support under U-Boot and SPL. The ENV size and
> offset,
> ported from U-Boot 2013.01 Marvell version: 2015_T1.0p16
>
> To create U-Boot image for SPI flash, user would need to replace
> * CONFIG_MVEBU_SPL_BOOT_DEVICE_MMC
On Wed, 2018-11-28 at 16:59 +0800, Aditya Prayoga wrote:
> Enable Marvell I2C driver and set default bus to external I2C bus.
> Define I2C aliases in device tree so it can be recognized by the
> driver.
>
> Signed-off-by: Aditya Prayoga
> ---
> arch/arm/dts/armada-388-helios4.dts | 2 ++
>
I would strongly prefer to keep the addresses consistent across
platforms in u-boot. Is there bugs you are seeing as a result of this?
Dennis
On Wed, 2018-11-28 at 16:59 +0800, Aditya Prayoga wrote:
> Use the values from U-Boot 2013.01 Marvell version: 2015_T1.0p16
>
> Signed-off-by: Aditya
El lun, 26-11-2018 a las 19:44 -0500, Paul Frields escribió:
> On Mon, Nov 26, 2018 at 5:47 PM Dennis Gilmore
> wrote:
> > El lun, 26-11-2018 a las 17:14 -0500, Josh Boyer escribió:
> > > Because the people that would be tasked with doing the
> > > development are
&
1 - 100 of 10959 matches
Mail list logo
