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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A7379DCD7@G01JPEXMBYT01>
Date:	Wed, 8 Jun 2016 02:27:14 +0000
From:	"Izumi, Taku" <izumi.taku@...fujitsu.com>
To:	Gabriele Paoloni <gabriele.paoloni@...wei.com>,
	"liudongdong (C)" <liudongdong3@...wei.com>
CC:	Linuxarm <linuxarm@...wei.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [bug discuss] fjes driver call trace warning, "PNP0C02" used in
 fjes	seems like a bug,

Dear Gab,

> > > > I think that "PNP0C02" should be used to mark any motherboard
> > reserved
> > > > resource and not a specific network driver.
> > > > It seems like a bug in the "fjes" driver.
> >
> >   Extended Socket network device is a shared memory based high-speed
> >   network interface between Extended Partitions of PRIMEQUEST 2000 E2
> >   series. To check if firmware supports Extended Socket network device,
> >   we take use of  "PCP0C02" device and special strings in DSDT.
> >
> >   "fjes" is not only "platform device driver (mainly act as network
> >    driver" but also "acpi driver" . If "PCP0C02" found and it is for
> >    Extended Socket network device, platform_device will be created.
> 
> From my understanding PNP0C02 is not a valid ACPI device HID but it is
> to be used only to reserve motherboard resources.
> 
> Can you please explain your identifier choice?

   Sorry for late.

   Extended Socket network device is not a physical device. This is a
   kind of virtual device in memory region which firmware provides.  
   This driver retrieves resource information 
   (memory reagion address firmware provides and so on)
   via PNP0C02. This resource is firmware reserved resources so we use
   PNP0C02.

   Sincerely,
   Taku Izumi

> 
> Gab
> 
> >
> >   Sincerely,
> >   Taku Izumi
> >
> > > >
> > > > Thanks
> > > >
> > > > Dongdong
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > linuxarm mailing list
> > > > linuxarm@...wei.com
> > > > http://rnd-openeuler.huawei.com/mailman/listinfo/linuxarm

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ