lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2564536c.449f.1823950ce01.Coremail.slark_xiao@163.com>
Date:   Tue, 26 Jul 2022 15:02:53 +0800 (CST)
From:   "Slark Xiao" <slark_xiao@....com>
To:     chandrashekar.devegowda@...el.com, linuxwwan@...el.com,
        chiranjeevi.rapolu@...ux.intel.com, haijun.liu@...iatek.com,
        m.chetan.kumar@...ux.intel.com, ricardo.martinez@...ux.intel.com
Cc:     netdev@...r.kernel.org
Subject: t7xx support and long term palnning

Hi all,
   As far as I know, MediaTek would release T8xx in the coming days. 
   In the latest kernel, we have supportted MediaTek platform with name t7xxx.
  So I want to know how should we extend the support for t8xx device? Use the same driver t7xx for current t7xx device or we will add a new driver for that?
  For QC chip or Intel chip, I saw they shared a same driver for different platform, such as QC sdx24, sdx55, sd65. I hope MediaTek may also use its vendor name or something else other than a product or serial name as it's driver name.
   So what's the planning of MediaTek?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ