I recently tried to compile my driver developed for the Kernel 5.9.16 using the
latest upstream version checked out from git and figured out that there is no
more MODULE_SUPPORTED_DEVICE macro.
Could you please give a hint where to look at for the information on why it was
removed?
--
Regar
On Sun, 22 Aug 2021 at 19:51, Ezequiel Garcia
wrote:
> In other words, IMO it's best to expose the NAND through UBI
> for both read-only and read-write access, using a single UBI device,
> and then creating UBI volumes as needed. This will allow UBI
> to spread wear leveling across the whole devi
On Wed, 21 Jul 2021 at 22:59, Pintu Agarwal wrote:
>
> On Wed, 21 Jul 2021 at 22:40, Mikulas Patocka wrote:
>
> > > >
> > > > Try to set up dm-verity with block size 512 bytes.
> > > >
> > > > I don't know what block size does squashfs use, but if the filesystem
> > > > block size is smaller than
On Mon, 30 Aug 2021 at 22:25, Thomas Petazzoni
wrote:
>
> Hello,
>
> On Mon, 30 Aug 2021 21:55:19 +0530
> Pintu Agarwal wrote:
>
> > Sorry for coming back to this again..
> > Unfortunately, none of the options is working for us with squashfs
> > (bootloader, initramfs).
> > initramfs have differe
Hello,
On Mon, 30 Aug 2021 21:55:19 +0530
Pintu Agarwal wrote:
> Sorry for coming back to this again..
> Unfortunately, none of the options is working for us with squashfs
> (bootloader, initramfs).
> initramfs have different kinds of challenges because of the partition
> size issue.
> So, our p
Hello,
On Mon, 30 Aug 2021 23:48:40 +0530
Pintu Agarwal wrote:
> ohh that means we already have a working reference.
> If possible can you share the details, even 4.19 or higher will be
> also a good reference.
>
> > > Or, another option is to use the new concept from 5.1 kernel that is:
> > >
so I got this macro which depends upon config choices to work,
Id like to have alt-config versions which throw some obvious error.
like this:
#elif (defined(CONFIG_DYNAMIC_DEBUG_CORE) && !defined(DYNAMIC_DEBUG_MODULE))
#define DEFINE_DYNAMIC_DEBUG_CATEGORIES(fsname, var, bitmap_desc, ...) \
BUI
trimming out the "noise", Im left with
>39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
> | ^~
> /home/jimc/projects/lx/wk-next/include/linux/dynamic_debug.h:283:9:
> note: in expansion of macro ‘BUILD_BUG_ON_M
i wrote a patch that got rejected because it did not apply cleanly to
the tree of greg kh
https://lkml.org/lkml/2021/8/18/304
the file i modified is
drivers/staging/rtl8723bs/include/rtl8192c_recv.h
get_maintainer.pl gave me the list of emails to send the patch to,
and i used it for that purpose.
Any inputs on this?
On Sun, Aug 29, 2021 at 11:42 PM Raul Piper wrote:
>
> Hello,
> I tried cross compiling the bluez and ported it to my linux platform.I
> think i have done it correctly as I am able to launch the gatt-service
> example successfully but i am not able to view it on the Smartphon
10 matches
Mail list logo