-----Original Message-----
From: Jason Gunthorpe <jgg@nvidia.com>
Sent: Wednesday, August 18, 2021 11:46 AM
To: Nikolova, Tatyana E <tatyana.e.nikolova@intel.com>
Cc: dledford@redhat.com; leon@kernel.org; linux-rdma@vger.kernel.org
Subject: Re: [PATCH] irdma: Add ice and irdma to kernel-boot rules

On Thu, Aug 12, 2021 at 11:33:04PM +0000, Nikolova, Tatyana E wrote:

quoted

quoted

quoted

@@ -12,6 +12,7 @@ ENV{ID_NET_DRIVER}=="bnxt_en",

RUN{builtin}+="kmod load bnxt_re"

quoted

 ENV{ID_NET_DRIVER}=="cxgb4", RUN{builtin}+="kmod load iw_cxgb4"
 ENV{ID_NET_DRIVER}=="hns", RUN{builtin}+="kmod load hns_roce"
 ENV{ID_NET_DRIVER}=="i40e", RUN{builtin}+="kmod load i40iw"
+ENV{ID_NET_DRIVER}=="ice", RUN{builtin}+="kmod load irdma"

This should not be needed, right? The auxbux stuff triggers proper
module autoloading?

Hi Jason,

Our module depends on the auxbus, but we don't know how the auxbus
could trigger loading of irdma. Could you please explain?

It should simply happen automatically once the aux device is created. If it
doesn't something is missing in the kernel.

It works the same way as any loading a module for any other struct device,
the aux device exposes a modalias and the userspace matches it to the
modules.alias file and then loads the specified module.

Thank you for the explanation. The modalias is exposed by the aux device as you described.

Tatyana