Re: [PATCH 10/10] PCI, sparc: clip firmware assigned resource under parent bridge's

Hi, Am I missing something or is this just code to get the the resource subsystem to accept the bus resources, not caring if the resources are actually usable? PCI BARs usually have a given size for a reason? - Kjetil Oftedal On 12/01/2015, Yinghai Lu ying...@kernel.org wrote: Some bios put

Re: [RFC PATCH 0/13] sparc32: sunset sun4m and sun4d

re the sparc kernel-developers don't have access to any real sparc32 hardware. SUN machines were at least plentiful. The LEON-family of processors being targeted towards the rad-hardened market are not so much available. Maybe Gaisler can contribute some systems, or make some available remotely? Best regards, Kjetil Oftedal

Re: [PATCH] sparc: Remove redundant copy of the LGPL-2.0

gt; > Applied. > Shouldn't the SPDX license identifiers in in arch/sparc/lib be adjusted to reflect the original intent of LGPL licensing? - Kjetil Oftedal

Re: [RFC PATCH 00/35] Move all PCIBIOS* definitions into arch/x86

n > a few places. > > I think it's completely separate, as you say, and we should defer it > for now because even part a) is a lot of work. I added it to my list > of possible future projects. > What about strange PCI devices such as Non-Transparent bridges? They will require their own PCI Config space accessors that is not connected to a host bridge if one wants to do some sort of punch-through enumeration. I guess the kernel doesn't care much about them? Best regards, Kjetil Oftedal

Re: [PATCH] sparc: Remove redundant copy of the LGPL-2.0

t (C) > - > -This library is free software; you can redistribute it and/or > -modify it under the terms of the GNU Library General Public > -License as published by the Free Software Foundation; either > -version 2 of the License, or (at your option) any later version. > - > -This library is distributed in the hope that it will be useful, > -but WITHOUT ANY WARRANTY; without even the implied warranty of > -MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > -Library General Public License for more details. > - > -You should have received a copy of the GNU Library General Public > -License along with this library; if not, write to the Free > -Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. > - > -Also add information on how to contact you by electronic and paper mail. > - > -You should also get your employer (if you work as a programmer) or your > -school, if any, to sign a "copyright disclaimer" for the library, if > -necessary. Here is a sample; alter the names: > - > - Yoyodyne, Inc., hereby disclaims all copyright interest in the > - library `Frob' (a library for tweaking knobs) written by James Random > Hacker. > - > - , 1 April 1990 > - Ty Coon, President of Vice > - > -That's all there is to it! > -- > 2.21.0 > > Looks like something has gone "wrong" in this part of the kernel tree. I guess the intention of the COPYING.LIB file was to license the contents of the sparc/lib folder under LGPL so that optimized standard C functions can easily be shared between the kernel and any userland libc using LGPL. In b24413180f5600bcb3bb70fbed5cf186b60864bd (License cleanup: add SPDX GPL-2.0 license identifier to files with no license) all these files were suddenly (re)licenced under GPL-2.0. Best regards, Kjetil Oftedal

Re: [PATCH 10/10] PCI, sparc: clip firmware assigned resource under parent bridge's

Hi, Am I missing something or is this just code to get the the resource subsystem to accept the bus resources, not caring if the resources are actually usable? PCI BARs usually have a given size for a reason? - Kjetil Oftedal On 12/01/2015, Yinghai Lu wrote: > Some bios put ra